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?
Probably not. This seems either like an issue with our internal tooling or a wrong expectation.
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.
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.
Probably use this bz for documentation purpose as only this arch will a different name for base image in all our docs.
(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.