-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Docker image does not work for Raspberry Pi #24
Comments
could this be an arm specific Dockerfile in this repo? |
Yeah, maybe. Or we could have a script that check /proc/cpuinfo or output from uname and fetch the right one |
So far I've been running picoroom.hendrikpeter.net straight on a pi without docker sitting in-between. If you really want to use docker you could always download this repository, copy the Dockerfile, name it "Dockerfile.arm64" and replace FROM line.
and replace all instances of I believe this issue might actually have been covered in this pull req: #10 |
Hi all, some time ago I was playing around with faasd and they have multi-arch Docker templates that can be used. My notes can be found here: https://gitlab.com/mkroehnert/faasd-on-raspberry#create-function-for-running-on-arm-faasd |
If you are running a Raspberry Pi 3 or 4 or 400, consider migrating to arm64 architecture. It took until the last few months to be released due to technical debt on older, unsupported Pi devices, but it is fully supported on these more recent revisions. Images available at https://downloads.raspberrypi.org/ To build on armhf you could try this variation of the option listed above. No idea on if it will work:
|
The Dockerfile adds an intel specific tini binary. The docker build goes though, but it does not work. Instead you get
cannot execute binary file: Exec format error
when starting the docker image.For my rasperry pi it works if i fetch the armhf specific binary:
https://github.com/krallin/tini/releases/download/v0.19.0/tini-armhf
This should probably be resolved automatically somehow, or maybe provide a workaround in the instructions.
The text was updated successfully, but these errors were encountered: