Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
When using repo discovery to pull containers from Docker.io registry, containers from main namespace (without slash in name) will fail to sync afterwards.
The problem is that while repo discovery works against `index.docker.io`, containers must be properly namespaced to be pulled from it. So instead of `alpine`, `library/alpine` must be pulled.
It seems that `library` is implicit when pulling images from `registry-1.docker.io`, so just `alpine` will work; but repo discovery doesn't work against that host, which means manual creation of repositories.
While this might be problem on Docker.io side, they are the biggest provider of images out there, so we might want to adjust to them nevertheless.
Version-Release number of selected component (if applicable):
Sat 6.5 snap 2
katello-3.9.0-0.11.rc2.el7sat.noarch
satellite-6.5.0-3.beta.el7sat.noarch
foreman-1.20.0-0.17.RC2.el7sat.noarch
Steps to Reproduce:
1. Content -> Products -> Repo discovery -> Type: Container images
2. Registry: index.docker.io -> Registry Search Parameter: alpine
3. Select `alpine` and `alpine/git` -> Create Selected -> Run repository creation
4. Navigate to product page, sync both repositories
Actual results:
Syncing `alpine` repository fails; syncing `alpine/git` succeeds.
To make alpine sync, go to details page and do either of following:
- change Registry URL to `https://registry-1.docker.io/`
- change Upstream Repository Name to `library/alpine`
Expected results:
Syncing both succeeds.
Moving this to the pulp team. Being tracked in https://pulp.plan.io/issues/4374 .
Basically pulp needs to handle the docker logic as per the upstream bug.
@Miroslaw afaik official docker v2 registry is located at registry-1.docker.io
only v1 clients should hit the index.docker.io, for v2 workflows registry-1.docker.io should be used.
https://pulp.plan.io/issues/4374#note-3
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:1222