hmm not sure if there is something wrong or we need some kind of special handline for the ppc tagged containers.
i can reproduce this using just podman... i went to [1] and found centos-binary-aodh-api:03e7a3a58585eb6d751cb6ea765973241f12f2f9_6e3b098e_ppc64le so its definitely there
attaching the trace here but basically pulling _x86_64 is OK but pulling _ppc64le gives the error:
hmm not sure if there is something wrong or we need some kind of special handline for the ppc tagged containers.
i can reproduce this using just podman... i went to [1] and found centos- binary- aodh-api: 03e7a3a58585eb6 d751cb6ea765973 241f12f2f9_ 6e3b098e_ ppc64le so its definitely there
attaching the trace here but basically pulling _x86_64 is OK but pulling _ppc64le gives the error:
podman pull trunk.registry. rdoproject. org/tripleomast er/centos- binary- aodh-api: 03e7a3a58585eb6 d751cb6ea765973 241f12f2f9_ 6e3b098e_ ppc64le registry. rdoproject. org/tripleomast er/centos
==> Copying blob 1373db2e09f7 done
unexpected EOF
Error: error pulling image "trunk.
BUT rdoproject. org/tripleomast er/centos- binary- aodh-api: 03e7a3a58585eb6 d751cb6ea765973 241f12f2f9_ 6e3b098e_ x86_64 rdoproject. org/tripleomast er/centos- binary- aodh-api: 03e7a3a58585eb6 d751cb6ea765973 241f12f2f9_ 6e3b098e_ x86_64 11482a8a3dfc9ac c1da7d914492a3a 51335aa1fb27737 bc4d story1501rhel8c ontainers ~]$
podman pull trunk.registry.
Trying to pull trunk.registry.
==> Writing manifest to image destination
Storing signatures
bf4f198f1977056
[marios@