Hi Konstantin, after some investigation and collaboration with skopeo project, we managed to track down the root cause. The issue is filled [0] and a PR is on its way already. Fix will go into next upcoming bugfix release.
[0] https://pulp.plan.io/issues/3910 -------- Regards, Ina Panova Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." On Mon, Jul 23, 2018 at 11:22 AM, Ina Panova <[email protected]> wrote: > Hi Konstantin, > > It looks like it might be an issue with skopeo. > I was able to reproduce the error only if i convert with skopeo image to > v2s1. > Conversion and pull of v2s2 succeeds. > Docker pull from as a result of sync from registry succeeds. > > Pull of skopeo output v2s1: > $ docker pull localhost:1234/centos1:latest > Trying to pull repository localhost:1234/centos1 ... > unexpected end of JSON input > > Pull of skopeo output v2s2: > $ docker pull localhost:1234/centos2:latest > Trying to pull repository localhost:1234/centos2 ... > sha256:6ac335a2188c8fec30719d6fb137931f3b9b4c480f264116e05430455f7ad578: > Pulling from localhost:1234/centos2 > Digest: sha256:6ac335a2188c8fec30719d6fb13793 > 1f3b9b4c480f264116e05430455f7ad578 > Status: Image is up to date for localhost:1234/centos2:latest > > I will reach skopeo devs and follow-up with you later once there are some > updates. > Thank you for pointing out this issue! > > > >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
