Issue #3910
closed
docker pull fails with unexpected end of JSON input
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
Updated by dkliban@redhat.com over 6 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 41
Added by ipanova@redhat.com over 6 years ago
Added by ipanova@redhat.com over 6 years ago
Revision e04d8629 | View on GitHub
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.
Updated by ipanova@redhat.com over 6 years ago
- Status changed from NEW to POST
- Assignee set to ipanova@redhat.com
Updated by ipanova@redhat.com over 6 years ago
- Status changed from POST to MODIFIED
Applied in changeset e04d862918220ae14151b250761049c29cc16efd.
Updated by dkliban@redhat.com about 6 years ago
- Sprint/Milestone deleted (
2.18.0)
Added by ipanova@redhat.com about 6 years ago
Revision 2ea1a9ad | View on GitHub
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)
Added by ipanova@redhat.com about 6 years ago
Revision 2ea1a9ad | View on GitHub
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)
Updated by ipanova@redhat.com about 6 years ago
Applied in changeset 2ea1a9ad95e116ec348d77e427367067e5caee17.
Updated by ttereshc about 6 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
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.