-
-
Notifications
You must be signed in to change notification settings - Fork 197
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
Support for ARM/M1 [E: Unable to locate package docker-ce-cli] #103
Comments
Can I see the full build output? This can sometimes happen due to a transient network error so you may also try building again. I just tried building from scratch using the snapshot on public ECR:
Seems to work on my end. |
|
I'm following the steps outlined here |
Okay, firstly, my previous comment was a bit off base, because the admin image isn't actually based on
Which appears to be the same base image digest that you're using. And yet it still works for me. Here's the full output:
Can you try running a plain (Are you on a non-AMD processor architecture perhaps? Could that cause this?) |
Yeah I'm on an M1 so that is probably the issue :( I ran the install.bash scripts manually in the CLI for the rolling ubuntu image and failed again on docker-ce-cli with the same error as above |
Well, it probably boils down to the fact that APT is detecting you're on ARM and the Docker and Terraform repos don't provide ARM builds. I doubt the issues will stop there, though, since most downloads in general are architecture-specific, and a large chunk of the hundreds of languages supported by Riju involve downloading and installing an architecture-specific binary or tarball. It may be possible to run cross-architecture images in Docker. If someone can get that working, I'd certainly accept a pull request adjusting the build scripts to pass whatever Docker command-line options are necessary to get it to automatically enable cross-architecture execution when appropriate. I'll update the issue title now that we have an idea of the root cause. |
By providing the platform flag I was able to run the admin shell:
I also needed to downgrade node to 14.x (not sure if this is really related to the M1 issue though.)
But I'm pretty close now. I also opened a PR updating a few things in the selfhosting doc. |
Oh, awesome. So, if I understand correctly:
If that's the case then it sounds like all we need to do is explicitly add
Hmm interesting, what error were you getting with Node 16.x? |
Heap out of memory crash I believe |
Odd, I can't think of any reason that would be related to the Node version or processor architecture. |
Not sure either, happy to investigate more! |
Seems others are experiencing this issue on an M1 as well when targeting --platform=linux/amd64 |
Oh, yikes. I guess it would be good to document this limitation (and link to the upstream issue). |
Hi Radon! Thanks again for this great resource!
I'm having a problem building the admin shell:
make image shell I=admin
It says my ubuntu image is:
https://download.docker.com/linux/ubuntu hirsute/stable amd64 Packages
Error:
The text was updated successfully, but these errors were encountered: