Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
# docker pull brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7:7.6
Trying to pull repository brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7 ...
7.6: Pulling from brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7
no supported platform found in manifest list
I was told it should be arch-aware like in other arches.
Version-Release number of selected component (if applicable):
aarch64-image: 7.6-66
RHEL-ALT-7.6-20180829.0
How reproducible:
always
I'm not sure what's the right component, rhel-server-aarch64-container seems most relevant. docker-registry is no longer supported.
Frantisek, is this something related to image build?
Comment 2Frantisek Kluknavsky
2018-09-03 12:41:22 UTC
Probably not. This seems either like an issue with our internal tooling or a wrong expectation.
Comment 3Frantisek Kluknavsky
2018-09-03 13:40:39 UTC
As far as I could find out, it is probably intended behaviour. The way to get the image is 'docker pull brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7-aarch64'. Arm is not rhel, it is rhel-alt-something.
https://projects.engineering.redhat.com/browse/RCM-40475
If you believe otherwise, please reopen and explain.
Well, both ppc64le and s390x base images are based on RHEL-ALT contents instead of RHEL, but they both can be pulled by,
docker pull brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhel7:7.6
from different architectures. I don't see why aarch64 should be a special case here.
Comment 5Frantisek Kluknavsky
2018-09-04 13:00:29 UTC
Ok, let us ask release engineers. This is an issue about where to put the image after it is built, not about the image itself.
(In reply to Qian Cai from comment #4)
> Well, both ppc64le and s390x base images are based on RHEL-ALT contents
> instead of RHEL, but they both can be pulled by,
> ...
That is factually untrue.
Only the ARM image is sourced from rhel-alt.