Re: Nexus OSS 3.0.0 M7 - Problems with Docker Registry (proxy to DockerHub)
1,573 views
Skip to first unread message
Peter Lynch
Feb 29, 2016, 9:19:23 AM2/29/16
to Ingo Bente, Nexus Users
It looks like you are using the wrong remote url for the docker registry proxy repository.
Delete the existing proxy repository in Nexus and create a new one with a remote URL of https://registry-1.docker.io
That is the only remote URL that is considered valid for proxying the official Docker registry.
Delete the existing proxy repository in Nexus and create a new one with a remote URL of https://registry-1.docker.io
That is the only remote URL that is considered valid for proxying the official Docker registry.
I'm curious, what documentation implied you should use a remote URL other than https://registry-1.docker.io ? You happen to be the second user I know of who chose the wrong remote URL and this leads to very strange errors.
-Peter
On Mon, Feb 29, 2016 at 9:24 AM, Ingo Bente <ingo....@gmail.com> wrote:
Hi,--I am struggling to set up a local docker registry that proxies DockerHub.Docker Versionsdocker --versionDocker version 1.10.2, build c3959b1docker info | grep VersionServer Version: 1.10.2Kernel Version: 4.1.18-boot2dockerNexus ConfigI use the default Config that comes with Nexus. I added a new docker-group, where I added the default docker-hub repo. Thus, Nexus tries to use V1 of the Docker Hub registry:Error when doing a 'docker pull my.repo.com:19443/ubuntu'
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/967a398e-ef30-4397-b756-c433188dd24a%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.
Peter Lynch
Feb 29, 2016, 9:22:58 AM2/29/16
to Ingo Bente, Nexus Users
I should also mention there are known issues being worked on with Docker 1.10 support and Nexus 3 M7.
You can try using Docker 1.9.1 in the meantime, that will also help.
-Peter
Ingo Bente
Feb 29, 2016, 10:05:46 AM2/29/16
to Nexus Users, ingo....@gmail.com
Hi Peter,
When I configure DockerHub credentials in the HTTP Authentication section:
thanks for the help.
To be honest: I can't determine why there was the index URL configured as remote storage. This is fixed now. The documentation is correct: https://books.sonatype.com/nexus-book/3.0/reference/docker.html#docker-proxy.
I doubt that I have entered the index URL manually. But as I said, I was not able to figure out what happened there.
Still - it does not work. Here are the new logs when I do a
docker pull my.repo.com:19443/ubuntuWhen I omit the HTTP Authentication section:
2016-02-29 14:48:05,948+0000 WARN [qtp1024735925-690] USERNAME_OF_LOCAL_NEXUS org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: GET /v2/ubuntu/manifests/latest: 401 - org.sonatype.nexus.repository.docker.internal.V2Exception: access to the requested resource is not authorized
When I configure DockerHub credentials in the HTTP Authentication section:
2016-02-29 15:03:13,497+0000 WARN [qtp1024735925-691] USERNAME_OF_LOCAL_NEXUS org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: GET /v2/ubuntu/manifests/latest: 401 - org.sonatype.nexus.repository.docker.internal.V2Exception: access to the requested resource is not authorized2016-02-29 15:03:13,510+0000 WARN [qtp1024735925-691] USERNAME_OF_LOCAL_NEXUS org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: GET /v2/ubuntu/manifests/latest: 404 - org.sonatype.nexus.repository.docker.internal.V2Exception$ManifestUnknownByTag: manifest unknown2016-02-29 15:03:13,510+0000 WARN [qtp1024735925-691] USERNAME_OF_LOCAL_NEXUS org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: GET /v2/ubuntu/manifests/latest: 404 - org.sonatype.nexus.repository.docker.internal.V2Exception$ManifestUnknownByTag: manifest unknownSince I get a 401, and then a 404, I assume that authentication against DockerHub is working.
There are two 404s because I have both the DockerHub Proxy Repo and my hosted Docker Repo in the same Docker Group.
Cheers
Ingo
Ingo Bente
Feb 29, 2016, 10:10:23 AM2/29/16
to Nexus Users, ingo....@gmail.com
I should also mention there are known issues being worked on with Docker 1.10 support and Nexus 3 M7.You can try using Docker 1.9.1 in the meantime, that will also help.
Thanks. The funny thing is: Although I get the same error message as mentioned in the ticket, doing a push and a pull to my private, hosted docker repo works.
Reply all
Reply to author
Forward
0 new messages