-
-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Containers can't be build on M1 #19
Comments
Thank you for taking the time to open this. This is odd, because the I will investigate this further, but it seems the issue has to do with the curl request being blocked by your workspace. I suggest seeing if you can access the URL in your browser. I would double-check your DNS settings as well as firewall which could be blocking the request. |
Facing the similar issue as well on M1, looks like this is ARM-specific problem since there's a dude on Discord getting the same trouble. |
managed to resolve above Docker issue, not getting stuck here, when it is building the
|
While we are still looking for a fix, we suggest running the course in Gitpod: NOTE: The course tools are complex, and we have not confirmed every project/lesson will work in Gitpod either. gitpod-web3.mp4 |
a workaround for now, i downloaded the
|
Did some testing on my M1 Air last week and ran into this issue as well. I believe it's because Solana's install script takes the container's CPU type into account when deciding which version to download and install. And it seems that, unless a platform is specified, Docker will try to pull an Ubuntu image that's closest to the host's CPU type, which for M1 is aarch64 / ARM64. Then for Solana, it turns out there are no prebuilt aarch64 version for Linux, just x86_64 / amd64. There are other aarch64 builds, but only for Apple machines: https://github.com/solana-labs/solana/releases/tag/v1.14.2 It's possible to force Docker to build a container using x86_64 Ubuntu with But once you hit the Turns out that M1 / M2 CPUs don't support AVX or AVX2 instructions, which The easiest thing for people with M1 / M2 machines to do would be to use GitPod or something similar like @ShaunSHamilton mentioned. Then the container should be built on an x86 machine, and shouldn't run into the same issue with |
failing install on new M1 as well with devcontainer.json. |
[2022-10-22T18:26:00.652Z] l https:// 0.0s
|
it's worked. Thank you! |
not working for me |
@branddesade What errors can you see in the logs? |
works on my windows but not my m1 mac too |
This really needs a fix, Mac M\d based machines aren't exactly rare in the dev community. |
Project
Installation process
Lesson Number
Issue/Experience
I think it only supports linux for now?
Code and Screenshots
The text was updated successfully, but these errors were encountered: