Project

Profile

Help

Issue #3910

docker pull fails with unexpected end of JSON input

Added by ipanova@redhat.com about 3 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Docker:
Platform Release:
2.17.1
Target Release - Docker:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Sprint 41
Quarter:

Description


Output of:
skopeo copy --format v2s1 docker://busybox:glibc dir:existingemptydirectory
was tared uploaded to Pulp, published which enables to serve the content as of from docker registry.

docker pull fails with:

$ docker pull localhost:1234/centos3@sha256:783f7f77b803b74c2f4cf0d61cc27ec404b6896f285106ed0a61ddff37e79833
Trying to pull repository localhost:1234/centos3 ... 
unexpected end of JSON input

for more info and investigations see here https://github.com/containers/skopeo/issues/526#issuecomment-411901330

Associated revisions

Revision e04d8629 View on GitHub
Added by ipanova@redhat.com about 3 years ago

docker pull fails with unexpected end of JSON input

closes #3910 https://pulp.plan.io/issues/3910

json.load and json.dump reorderes manifest file. The "signatures" field is supposed to be at the end of the JSON, because docker while stripping the signatures operates on the raw bytes of the data, without regard to JSON structure.

Revision e04d8629 View on GitHub
Added by ipanova@redhat.com about 3 years ago

docker pull fails with unexpected end of JSON input

closes #3910 https://pulp.plan.io/issues/3910

json.load and json.dump reorderes manifest file. The "signatures" field is supposed to be at the end of the JSON, because docker while stripping the signatures operates on the raw bytes of the data, without regard to JSON structure.

Revision 2ea1a9ad View on GitHub
Added by ipanova@redhat.com about 3 years ago

docker pull fails with unexpected end of JSON input

closes #3910 https://pulp.plan.io/issues/3910

json.load and json.dump reorderes manifest file. The "signatures" field is supposed to be at the end of the JSON, because docker while stripping the signatures operates on the raw bytes of the data, without regard to JSON structure.

(cherry picked from commit e04d862918220ae14151b250761049c29cc16efd)

Revision 2ea1a9ad View on GitHub
Added by ipanova@redhat.com about 3 years ago

docker pull fails with unexpected end of JSON input

closes #3910 https://pulp.plan.io/issues/3910

json.load and json.dump reorderes manifest file. The "signatures" field is supposed to be at the end of the JSON, because docker while stripping the signatures operates on the raw bytes of the data, without regard to JSON structure.

(cherry picked from commit e04d862918220ae14151b250761049c29cc16efd)

History

#1 Updated by ipanova@redhat.com about 3 years ago

  • Description updated (diff)

#2 Updated by dkliban@redhat.com about 3 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 41

#3 Updated by ipanova@redhat.com about 3 years ago

  • Status changed from NEW to POST
  • Assignee set to ipanova@redhat.com

#4 Updated by ipanova@redhat.com about 3 years ago

  • Status changed from POST to MODIFIED

#5 Updated by dkliban@redhat.com about 3 years ago

  • Sprint/Milestone set to 2.18.0

#6 Updated by dkliban@redhat.com about 3 years ago

  • Sprint/Milestone deleted (2.18.0)

#7 Updated by dkliban@redhat.com about 3 years ago

  • Platform Release set to 2.17.1

#9 Updated by ttereshc about 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

#10 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF