RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Bug 1816137 - registry.access.redhat.com is missed in registries list
Summary: registry.access.redhat.com is missed in registries list
Keywords:
Status: CLOSED NOTABUG
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
high
high
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
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:
Environment:
Last Closed: 2020-03-23 14:59:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:

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
skopeo-0.1.32-4.git1715c90.module+el8.2.0+4954+2247e50d.x86_64
containers-common-0.1.32-4.git1715c90.module+el8.2.0+4954+2247e50d.x86_64

How reproducible:
always

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.search]
registries = ['registry.redhat.io', 'quay.io', 'docker.io']
# If you need to access insecure registries, add the registry's fully-qualified name.
[registries.insecure]
registries = []
# and add the registries fully-qualified name.
[registries.block]
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
ubi8-working-container
Note You need to log in before you can comment on or make changes to this bug.