standard_init_linux.go:207: exec user process caused "exec format error"
See original GitHub issueDescribe the bug
When I run docker with this container on Raspberry PI I see the following error:
standard_init_linux.go:207: exec user process caused "exec format error"
I think it may be related to that Raspberry PI 3 is ARM based.
Environment (please complete the following information):
- OS: ubuntu-18.04.2-preinstalled-server-armhf+raspi3.img.xz
Used app version:
- Docker: bpatrik/pigallery2:1.5.6-stretch
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:12 (5 by maintainers)
Top Results From Across the Web
exec user process caused "exec format error" - Stack Overflow
This can happen if you're trying to run an x86 built image on an arm64/aarch64 machine. You'll need to rebuild the image using...
Read more >standard_init_linux.go:207: exec user process ... - GitHub
The reason you are seeing this error is because the container was built for an amd64 processor (https://hub.docker.com/layers/thenetworkchuck/ ...
Read more >FIX (Solved): standard_init_linux.go:207: exec user process ...
issue: docker container not starting and exit with error: standard_init_linux.go:207: exec user process caused “exec format error”. Sto ...
Read more >Fix: standard_init_linux.go:228: exec user process caused
In this post, we'll discuss the error “standard_init_linux.go:228: exec user process caused: exec format error” and offer two fixes.
Read more >exec user process caused "exec format error" - balenaOS
I am getting an error after pushing to BalenaCloud 'standard_init_linux.go:207: exec user process caused “exec format error”' all my containers ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I managed to build working image on aarch64 (Raspberry Pi 3 B+) from this Dockerfile:
It should work for any architecture which is supported by node docker image.
Hi
Yes its the issue with the ARM based architecture. I tried to quickly create an arm32v7 based docker image (see here), but it was not that straightforward. It might take some time for me to figure out the solution. In the meantime you can try:
Update: This might be it. As far as I understand [1, 2], there isn’t any straightforward way of building an arm based image on (a x86 based) docker hub. I’ll update the document to reflect this and leave the arm based container there if someone wants to build the image.