-
Notifications
You must be signed in to change notification settings - Fork 85
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
pull command gets wrong architecture for recently updated official images #1025
Comments
I forgot to mention, nothing unusual is found in syslog after this happens, just the normal "shim started" and "shim reaped" from |
OK, so At Docker Hub, one can see that an In fact, the image I get when I do that (or On the other hand, if I explicitly pull the digest the Hub lists for armv6 ( Any idea as to what is going on here? Why is it not pulling the right image automatically? And why is the image that it does pull not found on the Docker Hub at all? Lastly, shouldn't there be an error message somewhere when exec() fails? In this case it probably returned ENOEXEC which would have made the problem a lot more obvious. |
OK as of today, the previously working It was updated "a day ago" according to Docker Hub, I'm guessing this isn't a coincidence. As with the other images, it works if you find the correct digest for the linux/arm/v6 arch on the Docker Hub website and pull that explicitly, i.e. in this case When just pulling |
Having this problem too. I think it might not be anything to do with
You can see that Either way this is pretty annoying, makes it hard to do multi-architecture projects. |
Expected behavior
Using a first-generation Raspberry Pi Model B, I expected to be able to run official images tagged with the
linux/arm/v6
architecture, likealpine
,node:alpine
ordebian:slim-stable
.Actual behavior
The three images listed above don't work: when attempting to start any new containers based on them, they exit immediately with no output. This happens regardless of the command specified, if any (e.g.
docker run -i --rm alpine /bin/echo hello
fails to produce any output), and regardless of the combination of-i
-t
or-d
flags.At least one image does work though:
nginx:alpine
, and it works using any command (e.g.docker run -i --rm nginx:alpine /bin/echo hello
prints "hello") and any mode (docker run -it --rm nginx:alpine /bin/sh
also works).I couldn't discern anything obviously different between the working and non-working images. The binaries within have identical
file
output: "LF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-armhf.so.1, stripped".Steps to reproduce the behavior
Simply install docker on a RaPi1B and try to run
alpine
or one of the other images mentioned above.This is using the latest official RaPi image (Raspbian buster) and Docker from get.docker.com (ended up with package version
5:19.03.11~3-0~raspbian-buster
from repohttps://download.docker.com/linux/raspbian
).Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)
The text was updated successfully, but these errors were encountered: