-
Notifications
You must be signed in to change notification settings - Fork 67
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
Use chef image clone to ghcr to workaround docker hub limits #714
Use chef image clone to ghcr to workaround docker hub limits #714
Conversation
There is an upstream bug asking Chef to push an image to GHCR: chef/chef#13907 |
cd92c2e
to
23e0dff
Compare
|
23e0dff
to
03c461f
Compare
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.
I mean I don't really have the knowledge to review the docker side of this.
Looking at the other repo it looks like you're actually rebuilding the image from scratch rather than just copying it? If the result is supposed to be the same same why does it apparently have a different root CA bundle that necessitates patching our cookbooks?
The only other obvious thing is that this changes all users to use the ghcr version not just the actions.
I use a The CA bundle issue is due to chef's bundled ruby seemingly using an old CA cert bundle. It is unrelated to Docker.
|
I created https://github.com/Firefishy/chef-docker-image which uses github actions to clone the official Chef docker image and push it to GHCR.
This is to avoid the extremely low docker hub download limits which are breaking our tests.