Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1816137 - registry.access.redhat.com is missed in registries list
Summary: registry.access.redhat.com is missed in registries list
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: container-tools-1.0-module
Version: 8.2
Hardware: x86_64
OS: Linux
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2020-03-23 12:19 UTC by Alex Jia
Modified: 2020-03-23 15:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-03-23 14:59:55 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

Description Alex Jia 2020-03-23 12:19:01 UTC
Description of problem:
Failed to pull ubi8 w/ short container image name, because 'registry.access.redhat.com' is missed in registries list
of /etc/containers/registries.conf.

Version-Release number of selected component (if applicable):

[root@hp-moonshot-01-c29 ~]# yum module list --installed|grep container
container-tools 1.0 [e] common [d] [i] Common tools and dependencies for container runtimes

[root@hp-moonshot-01-c29 ~]# rpm -q skopeo containers-common

How reproducible:

Steps to Reproduce:
1. buildah from ubi8

Actual results:

[root@hp-moonshot-01-c29 ~]#  buildah from ubi8
The following failures happened while trying to pull image specified by "ubi8" based on search registries in /etc/containers/registries.conf:
* "localhost/ubi8": Error determining manifest MIME type for docker://localhost/ubi8:latest: pinging docker registry returned: Get https://localhost/v2/: dial tcp [::1]:443: connect: connection refused
* "registry.redhat.io/ubi8": Error determining manifest MIME type for docker://registry.redhat.io/ubi8:latest: unable to retrieve auth token: invalid username/password
* "quay.io/ubi8": Error determining manifest MIME type for docker://quay.io/ubi8:latest: Error reading manifest latest in quay.io/ubi8: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 3.2 Final//EN\">\n<title>404 Not Found</title>\n<h1>Not Found</h1>\n<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>\n"
* "docker.io/library/ubi8": Error determining manifest MIME type for docker://ubi8:latest: Error reading manifest latest in docker.io/library/ubi8: errors:
denied: requested access to the resource is denied
unauthorized: authentication required

Expected results:

Additional info:

[root@hp-moonshot-01-c29 ~]# grep registries /etc/containers/registries.conf
# keep track of registries for various container backends.
# lists of registries.
# The default location for this configuration file is /etc/containers/registries.conf.
# The only valid categories are: 'registries.search', 'registries.insecure',
# and 'registries.block'.
registries = ['registry.redhat.io', 'quay.io', 'docker.io']
# If you need to access insecure registries, add the registry's fully-qualified name.
registries = []
# and add the registries fully-qualified name.
registries = []

A workaround is to use a fully-qualified container image name such as registry.access.redhat.com/ubi8

[root@hp-moonshot-01-c29 ~]# buildah from registry.access.redhat.com/ubi8
Getting image source signatures
Copying blob sha256:0bb54aa5e97745c8692f6fc54dadca5b4b645a724ba5df96ecb762626d083981
 69.73 MiB / ? [-------------=---------------------------------------------] 5s
Copying blob sha256:941e1e2b31a86bf0d41d8964e6f0559267859fe3893b518b0dbd605c60c1ffe7
 1.54 KiB / ? [------=-----------------------------------------------------] 0s
Copying config sha256:0c46e5c7a82a97d21447ee6a1ef0d407317642c9361b562456395e087be08774
 4.43 KiB / 4.43 KiB [======================================================] 0s
Writing manifest to image destination
Storing signatures

Note You need to log in before you can comment on or make changes to this bug.