Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionVladislav Walek
2016-11-30 16:49:23 UTC
Description of problem:
When trying to pull image from local docker registry, the incorrect digest is resolved. The image was 'docker save' from 1.8.3 version saved in tar, and 'docker load' using 1.10 and docker push to registry.
However when creating an application using the ImageStream Builder logs would print an error on the first line:
'error: build error: unabe to get registry/openshift3/httpd-24-rhel7@sha256:<digest>'.
But the registry was configured with SSL proxy (after running a while without SSL):
We have configured Docker Distribution in an unsecured manner (http on port 5000),
and later secure it with an httpd ssl proxy on port 443, we roughly followed this guide:
https://github.com/docker/docker.github.io/blob/master/registry/recipes/apache.md
And when trying:
1. pull the image - returned digest (manifest) is the invalid one.
2. Push the same image, digest returned (presumably calculated locally on docker client)
3. Attempt pull the invalid digest fails.
4. Attempt to pull the pushed digest succeeds.
The problem is that if the pull is done from the unsecured the digest is ok, if from SSL the digest is incorrect. The question is, is it caused by docker registry?
Running:
'docker-distribution-2.4.1-2.el7.x86_64'
Openshift Container Platform Cluster v3.3.0.32
kubernetes v1.3.0+52492b4
docker 1.10.3, from package: 'docker-common-1.10.3-46.el7.14.x86_64' commit: '5206701'
Version-Release number of selected component (if applicable):
Openshift Container Platform Cluster v3.3.0.32
How reproducible:
Actual results:
Expected results:
the digest should be same on ssl and non-ssl registry
Additional info:
Hi, I've received reply from customer:
Updating Docker-Distribution Package to version 2.5.0-1.el7.x86_64
Full Package Name: docker-distribution-2.5.0-1.el7.x86_64
Solves the issue!!!
Could you check it? Thx