Issue #4374
closedUnable to sync docker hub images from index.docker.io
Description
$ pulp docker repo create --repo-id=empowerment --feed=http://index.docker.io --upstream-name=alpine
Repository [empowerment] successfully created
$ pulp docker repo sync run --repo-id=empowerment
+----------------------------------------------------------------------+
Synchronizing Repository [empowerment]
+----------------------------------------------------------------------+
This command may be exited via ctrl+c without affecting the request.
Task Failed
Could not fetch repository alpine from registry http://index.docker.io -
Unauthorized or Not Found
Pulp has logic to say if its just the container name add "library" to it https://github.com/pulp/pulp_docker/blob/2-master/plugins/pulp_docker/plugins/registry.py#L301-L305 , unfortunately it only allows registry-*.docker.io . We need it to include index.docker.io also.
Updated by paji@redhat.com about 5 years ago
Addressed by https://github.com/pulp/pulp_docker/pull/304/files
Updated by ipanova@redhat.com about 5 years ago
paji thank you for the PR, but the index.docker io should be used only for registry v1 clients. Official Docker’s public v2 registry is located at registry-1.docker.io
Fox example consult docs please https://docs.docker.com/registry/spec/auth/token/#how-to-authenticate
i was not able to find anywhere where they explicitly confirm that, but looking for 'index.docker.io/v2/' will give you zero results. Everything points to registry-1.docker.io/v2/
also in our docs we state to use index.docker.io only for V1 content ( with a proper flag) https://docs.pulpproject.org/plugins/pulp_docker/user-guide/recipes.html#sync
Updated by daviddavis about 5 years ago
- Status changed from NEW to POST
- Assignee set to paji@redhat.com
Updated by daviddavis about 5 years ago
- Project changed from Infrastructure to Docker Support
Updated by rchan about 5 years ago
Remove "blocking 2.15.z" value - we are well past that build so no reason to tag as such.
Updated by daviddavis about 5 years ago
- Status changed from POST to CLOSED - NOTABUG
Talked to @paji and he said we should close this.