Feature #20773
closed
Support for Private Repos at Docker Hub
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1475121
Description of problem:
Satellite 6 is not able to sync private registry hosted on Docker Hub.
Version-Release number of selected component (if applicable):
How reproducible:
Allways
Steps to Reproduce:
1. Create a registry on https://hub.docker.com
2. Push an image in the registry and make the registry private
3. Create the Docker type repository in the Satellite pointing to the private registry
4. Try to sync the repository
Actual results:
Sync fails with following error:
Could not fetch repository username/registry from registry https://registry.hub.docker.com - Unauthorized or Not Found
Expected results:
- Unauthorized access is documented.
- Registry is synced.
Additional info:
- Registry entry in Containers > Registries is created and credentials are correct.
- If the registry is not set as Private, sync is working without any issues
- Pulling from the private registry works
Updated by Sebastian Gräßl over 7 years ago
- Subject changed from Support for Private Repos at Docker Hub to Support for Private Repos at Docker Hub
- Status changed from New to Rejected
Updated by Marek Hulán over 7 years ago
Sebastian, what was the reason for rejecting the issue?
Updated by Sebastian Gräßl over 7 years ago
@Marek: I copied the wrong ID and couldn't kill the script anymore. The BZ is about syncing of private repos via pulp. Private repos on Docker hub work with foreman-docker, however it is not explicitly documented.