workaround for docker push failing with "unknown blob"

[Daniel Hiller]

Hi everyone,

regarding the above issue which impacts several release jobs on our CI [1] infra we've experimented with replacing `docker push` with `skopeo copy` on our kubevirtci-publish build [2] in order to have a workaround in place.

Besides moby-engine skopeo [3] is also available in our  quay.io/kubevirtci/bootstrap and golang image and it seems to be a workaround for the time being [4]

Please see the moby issue we created for more details [5].

[1] https://search.ci.kubevirt.io/?search=unknown+blob&maxAge=336h&context=1&type=build-log&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

[2] https://github.com/kubevirt/kubevirtci/pull/749

[3] https://github.com/containers/skopeo

[4] https://storage.googleapis.com/kubevirt-prow/logs/publish-kubevirtci/1493715853890293760/build-log.txt

[5] https://github.com/moby/moby/issues/43234

--

Kind regards,

Daniel Hiller

He / Him / His

Senior Software Engineer, OpenShift Virtualization

Red Hat

dhi...@redhat.com   

Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, 
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill