Comment 1 for bug 1861342

Revision history for this message
Marios Andreou (marios-b) wrote :

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:

podman pull trunk.registry.rdoproject.org/tripleomaster/centos-binary-aodh-api:03e7a3a58585eb6d751cb6ea765973241f12f2f9_6e3b098e_ppc64le
==> Copying blob 1373db2e09f7 done
  unexpected EOF
Error: error pulling image "trunk.registry.rdoproject.org/tripleomaster/centos

BUT
podman pull trunk.registry.rdoproject.org/tripleomaster/centos-binary-aodh-api:03e7a3a58585eb6d751cb6ea765973241f12f2f9_6e3b098e_x86_64
Trying to pull trunk.registry.rdoproject.org/tripleomaster/centos-binary-aodh-api:03e7a3a58585eb6d751cb6ea765973241f12f2f9_6e3b098e_x86_64
==> Writing manifest to image destination
Storing signatures
bf4f198f197705611482a8a3dfc9acc1da7d914492a3a51335aa1fb27737bc4d
[marios@story1501rhel8containers ~]$