Project

General

Profile

Bug #25972

Can't sync discovered containers without slash in name from Docker.io registry

Added by Partha Aji over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

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.

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.

Associated revisions

Revision c490d55e (diff)
Added by Partha Aji over 3 years ago

Fixes #25972 - Better Docker Repo Discovery UI (#7957)

This commit tweaks the existing docker repo discovery workflow by
allowing the user to search from one of
1) Docker Hub
2) RH Registry
3) Quay.io
4) Custom - Private Registries

When the user chooses Docker Hub, the javascript knows that it has to
search in index.docker.io while create the repo using
registry-1.docker.io

Basic issue that this commit resolves is that "docker search foo"
searches for foo in index.docker.io, but "docker pull foo" pulls it from
registry-1.docker.io. This causes issues when creating repos from
Discovery. This commit tries handle that situation with a better
workflow.

Revision 1625f449 (diff)
Added by Mirek Długosz over 3 years ago

Refs #25972 - default value and class for Registry to Discover

c490d55ed1012aac08e10dacc4e581d19125fbea introduced new <select>
'Registry to Discover'. There are two issues with it:

1. It uses default browser styling, making it stand out from other
elements on form.

2. It has no default value set. Empty string is used automatically
instead. As result, when user clicks it for the first time, there are 5
items available. After picking one, all subsequent click will display
only 4 items.

This commit fixes both of these issues.

Revision 38587f48 (diff)
Added by Mirek Długosz over 3 years ago

Refs #25972 - use registry.redhat.io

Red Hat maintains three container registries:
registry.access.redhat.com, registry.redhat.io and
registry.connect.redhat.com. The plan is to eventually decommission
registry.access.redhat.com.

Use registry.redhat.io as default. registry.access.redhat.com can still
be used by selecting Custom and providing url manually.

History

#1 Updated by Partha Aji over 3 years ago

  • Bugzilla link set to 1648344

#2 Updated by The Foreman Bot over 3 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7957 added

#3 Updated by Anonymous over 3 years ago

  • Status changed from Ready For Testing to Closed

#4 Updated by The Foreman Bot over 3 years ago

  • Pull request https://github.com/Katello/katello/pull/7966 added

#5 Updated by The Foreman Bot over 3 years ago

  • Pull request https://github.com/Katello/katello/pull/7967 added

#6 Updated by Justin Sherrill over 3 years ago

  • Triaged changed from No to Yes
  • Target version set to Katello 3.12.0

Also available in: Atom PDF