-
Notifications
You must be signed in to change notification settings - Fork 597
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
re-enable arm32v6 and arm32v7 builds #447
Conversation
Builds for these architectures were broken for some time, but this should be resolved now, so we can re-enable these (fingers crossed). This reverts commit 461a3ec. Signed-off-by: Sebastiaan van Stijn <[email protected]>
CI looks happy, and I see some |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully built arm32v6
and arm32v7
locally with qemu-user-static and also built arm32v7
on an arm64v8
aws server.
Thanks for checking! |
I tested on an arm32v7 box and they seem OK; my v6 box is less accessible, so it seems pretty reasonable IMO to roll the dice and assume it's fixed. 😄 |
Changes: - docker-library/docker@52a2206: Merge pull request docker-library/docker#447 from thaJeztah/reenable_arm32 - docker-library/docker@b0550bb: re-enable arm32v6 and arm32v7 builds
Changes: - docker-library/docker@c0e8bf9: Merge pull request docker-library/docker#448 from infosiftr/remove-23 - docker-library/docker@ff78b7b: Remove version 23.x - docker-library/docker@52a2206: Merge pull request docker-library/docker#447 from thaJeztah/reenable_arm32 - docker-library/docker@b0550bb: re-enable arm32v6 and arm32v7 builds
Builds for these architectures were broken for some time, but this should be resolved now, so we can re-enable these (fingers crossed).
This reverts commit 461a3ec.