-
Notifications
You must be signed in to change notification settings - Fork 24
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 pull via manifest on a rpi 1 device (armv6l) will not pull the arm/v6 image, but the arm/v7 image if any #4
Comments
See also moby/moby#41017 |
This was fixed in containerd/containerd#4530, which got pulled into Docker in moby/moby#41688, and was officially released in v20.10.0. 👍 |
Not sure if this is the best place to comment, or if I should open another issue, but I'm getting the same problem with docker v20.10.8. I'm on rasbperry pi zero w, it should be pulling armv6 but pulls armv7 instead and fails. |
Implements Wordaround for #3 and #4 issues : * Travis + CicleCI build refactoring (=> Stop multiplying binaries releases on docker hub) * Implement a workaround for biarms/mysql#4 * Improve doc
Because of this bug, the version "5" of "biarms/mysql" - as well as the "latest" tag - was 'hacked' to expose only one 'arm/v6' image, and not the 'arm/v7' one (while this image exists in this repo).
That way, the end-user will receive a 'startable image' for his device, even if it is not the more accurate one.
The text was updated successfully, but these errors were encountered: