Xenial docker image creates/observes bogus hash sum mismatches. #51
Comments
Here's how to reproduce this problem: It turns out that the problem only seems to exist for Xenial Xerus Docker image only - not in Xenial outside of Docker. Below is how to reproduce the problem: Just to make sure I had the good version of Xenial, I deleted my locally cached image and pulled a fresh copy. It made no difference. The relevant Dockerfile is below:
Here's the resulting error message:
This is something wrong with the Docker image - since the problem only occurs under Docker - not on "normal" OS installs. Maybe a missing dynamic library?? |
I'm one of the Neo4j Docker image maintainers. I'm very interested to understand what's going on here and happy to collaborate on any changes that are needed. @tianon do you have any ideas? |
@benbc I'm tied up for the next 10 days or so - but here's a thought about how to diagnose the problem if you have time. Do an strace of the apt-get install both inside the container and on a VM or bare metal machine, and look for failed calls that occur inside the container that don't occur in the VM. You're probably looking for a failed stat or open. If you filtered for that particular circumstance, then that's likely to be a file that's missing. Not all missing files cause programs to fail outright. My guess is that there's a missing library that's dynamically loaded. This is a pretty effective technique - but it can be tedious :-(. |
Here's what I've done so far to try and narrow this down:
Next thing I'm trying is exploding the Docker rootfs to compare to the chroot bit by bit and see what falls out. |
Ooh, it might be that we have this in our
This forces |
It looks fixed to me too. Neo4j gets installed, my tests run. Two fail - but not for things related to that. @tianon: Did you make a change to that apt.conf file? |
Hi, I'm experiencing the same issue with a "real" installation of Ubuntu 16.04 (desktop) - which is actually an upgrade from 15.10. I don't remember having this issue last week. Now I have this:
I tried to clean using Any hint on this one ? Cheers |
@tsde, that looks like moby/moby#23203, which is fixed 🎉 @Alan-R and @benbc looks like the original issue is fixed now? |
The original issue we were having seems to have been fixed for over a week. I'm guessing that @tsde's problem was separate. Since I'm currently in the process of putting out a release, I'll notice if it's broken again, and let you know. It seems unlikely. Speaking of which - does anyone know what went wrong here, and what was done to fix it? "Problems that go away by themselves, come back by themselves" - Sarah Kiefhaber |
Attn @tianon, @benbc: It's broken again... |
FWIW: I got the same result with 3.0.1. I removed my local copy of xenial before doing the first one above. |
This is an issue with the hashes of the http://debian.neo4j.org/repo repository, not this image (and is likely fixed by now, given the age of the previous comments 😅). The default configuration of this image helps to show the problem more readily by preferring the Please file any further issues with the maintainers of the repository which exhibits the issue. Thanks! 👍 |
This started out as a problem with Neo4j, but it has evolved into some kind of a problem with the Xenial build on DockerHub. This is a problem which only exists in the Docker image, and not any any known "real" installation. Details are provided here:
The text was updated successfully, but these errors were encountered: