vouch-proxy
vouch-proxy copied to clipboard
migrate docker builds from Docker Hub to quay.io
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
@Herbrant Docker Hub no longer builds containers triggered by a push to GitHub on their free tier.
I've established service at quay.io.. https://quay.io/repository/vouch/vouch-proxy
these all work...
docker pull quay.io/vouch/vouch-proxy:latest
docker pull quay.io/vouch/vouch-proxy:0.28.0
docker pull quay.io/vouch/vouch-proxy:alpine-latest
docker pull quay.io/vouch/vouch-proxy:alpine-0.28.0
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 Pricing: https://github.com/features/packages#pricing
this is looking much better.. https://quay.io/repository/vouch/vouch-proxy?tab=tags
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?
I have some PIs available and I would be willing to support this effort, as I'm using vouch-proxy
on my home network on arm as well.
If I understand correctly, the clean way here would be to migrate to a multi-arch image, which means building the manifest or using buildx
to build the image? Or what exactly is missing, and how could I help @bnfinet?
@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.