-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Latest Docker Image Corrupted? #7
Comments
This doesn't seem like an issue with the upstream container.
|
Here's the image ID for my image anyway.
|
Gah... this is probably related to #5 And I've been debugging the rpmdb issue quite a while over in geerlingguy/ansible-role-kubernetes#67 |
I'm thinking the update pushing the new version of the |
Ah... and just found this:
|
My thought is to let CentOS manage the update of their base image. You just keep your image down to installing Python bits you need and ansible. And yes if you have to install packages and updates do it in one command.
thoughts? |
Yeah, I think I'll go that route. For CentOS 6 and 7, I always ran a general Just pushed up a commit that may fix it, but it will be 20-30 min before it's built on Docker Hub. |
@geerlingguy Thanks for the help, these images are really useful! |
@dmlb2000 - New image is up; can you see if it works for you now? |
@geerlingguy I'm able to install things, but we are having issues with GPG keys now... so an update doesn't seem to work for example and I refuse to think the GPG key for |
Before:
After:
So it seems it's not corrupt out of the box, at least. And yeah, I'm seeing GPG key issues too—over in geerlingguy/ansible-role-kubernetes#67 I re-ran the tests but it's still just adding GPG keys over and over and getting some errors there in CI :( |
I'm guessing there's some sort of package we are missing to install. |
Just testing a
So I found: https://bugs.centos.org/view.php?id=16655 — which is pretty much the same issue. I tried on the |
I just pushed another commit that basically strips the cache-related operations, and just does a
|
Yup seems like the base image without the cache manipulations works, you can run for example...
But it doesn't work on your image, might be the cache issue. |
Weird. Image is built, I pulled it, and still getting the GPG issues. Now I wonder if one of the packages here is causing the issue:
|
Try adding the |
The plot thickens... If I build the image on my local workstation (exact same
It succeeds. If I build the image on Travis CI or Docker Hub and do the same, I get the GPG key errors. So something about the Docker installation/configuration on Travis CI and Docker Hub seems to be causing this issue. Grr. |
It's the Linux hosts they run to do the build? Do you run a Mac? |
Yeah I'm on macOS. |
Yup ran it on my CentOS 7 server and reproduced the GPG error locally |
Seems to not produce GPG errors on my CentOS 7 server |
Then I can run a |
Seems like removing the update also works. |
The CentOS guys need to rebuild their image so that updates don't apply later and corrupt their base image. This fix seems to work for me. Fix geerlingguy#7 Signed-off-by: David Brown <[email protected]>
@dmlb2000 Testing that on Docker Hub... thanks for helping debug this! |
@geerlingguy Just pulled the image seems to work fine now! |
Yay! Confirmed here too. |
Jeff,
I think the latest image that got pushed to hub.docker.com has a corrupted RPM database in it for some reason.
The text was updated successfully, but these errors were encountered: