Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Can't pull from docker.io explicitly, 500 error or #845
I have a maven configuration that was working until this weekend, where we're setting a custom registry to pull from/push to by default in the parent, and then for a couple specific images that inherit from public images, we set a
For example, I have a Dockerfile that's
Mac mvn -X output:
Ubuntu bamboo mvn -X output:
I can pull manually just fine on both the boxes:
As you can see it definitely forgets our custom registry and understands it's trying to get from docker.io - it just fails. I have tried registry-1.docker.com, registry.docker.com, registry.hub.docker.com, and various other permutations of .io/.com and hostnames to no good effect.
This was working until the 19th; we didn't change code, poms, or versions. Then it started failing on the 20th. Any thoughts are welcome.
for the ubuntu bamboo server, it's Maven 3.3.
I seem to have the same or very similar problem. My docker daemon debug logs show this when a Jenkins build attempts "mvn docker-maven-plugin:0.21.0:build"
If ssh to the jenkins slave and run the same exact mvn command in the workspace of the jenkins build, it succeeds and docker daemon log shows this:
The build broke during the weekend, no changes were made to the project, to Jenkins setup etc.
Thanks for the report, but unfortunately I can't reproduce it here (with Docker for macOS). Do you have a sample pom.xml how I could reproduce the error ?
The logs above ("Unable to pull 'debian:sid' from registry 'docker.io' : Could not reach any registry endpoint") sound like that the Docker daemon cannot reach out to docker.io (so might be a network issue, too). For registry related issues it is important to note that its the Docker daemon which tries to contact the registry, never the client (cli, d-m-p) itself. So fo comparing runs its important to use the same Docker daemons (just mentioning it).
Well dip me in honey and call the bears, that fixes it! I was on 1.8.0_112-b16 but upgrading to 1.8.0_144 has made the issue go away. Thanks all! So for future searchers, if you're using docker-maven-plugin, or I guess any other maven plugin or java scheme for downloading container images (?) from docker.io, upgrading your Java version to at least .144 will get you going again.
Thanks to everyone who pitched in to find this.