-
Notifications
You must be signed in to change notification settings - Fork 327
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
migrate docker builds from Docker Hub to quay.io #406
Comments
@Herbrant Docker Hub no longer builds containers triggered by a push to GitHub on their free tier. I've established service at quay.io.. these all work...
The arm based build is still configured to push to Docker Hub. I'll leave this open until that's fixed and the README is updated. |
Thank you! @bnfinet |
Now we're getting a build error on quay... "Could not pull base image: API error (500): toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" https://quay.io/repository/vouch/vouch-proxy/build/9b4f2d79-2d30-4572-ba1c-4ad2ef201b1e |
I think we can use Github actions and Github packages, it should be free for public repositories. https://docs.github.com/en/actions/guides/publishing-docker-images |
this is looking much better.. |
the ARM builds are still on docker hub, only with the tag "latest-arm". Would it be possible to add version tag too? |
How exactly could we help to get the ARM images back? If I understand correctly, the clean way here would be to migrate to a multi-arch image, which means building the manifest or using |
@sambernet pretty sure the arm image here is current... https://hub.docker.com/r/voucher/vouch-proxy/tags The broader effort of completing the full migration to quay.io is still needed, including proper tagging and versioning. Help would be appreciated. If you're up for reviewing the relevant items in the '.github' directory and offering some suggestions or a PR that'd be much appreciated. |
Hi! Can you update the Dockerhub's image for amd64? It seems that only the arm version is updated to the latest commit.
Thanks in advance!
@mario-tux
The text was updated successfully, but these errors were encountered: