fix(docker): add a custom policy.json file in the RHDH image for pulls to work correctly [RHDHBUGS-2799]#4385
Conversation
…s to work correctly [RHDHBUGS-2799] This contains a specific identity mapping for pulls against registry.access.redhat.com/rhdh. For some reason, Skopeo would fail otherwise with "Source image rejected: None of the signatures were accepted". This cherrypicks 8ba897d. ref: https://issues.redhat.com/browse/RHDHBUGS-2799
policy.json file in the RHDH image for pulls to work correctly [RHDHBUGS-2799]
policy.json file in the RHDH image for pulls to work correctly [RHDHBUGS-2799]policy.json file in the RHDH image for pulls to work correctly [RHDHBUGS-2799]
|
/cc @nickboldt |
|
The container image build workflow finished with status: |
|
/test e2e-ocp-helm |
|
/test e2e-ocp-helm |
…from-registry.access.redhat.com-source-image-rejected-none-of-the-signatures-were-accepted--main
|
/test e2e-ocp-helm |
|
This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days. |
…from-registry.access.redhat.com-source-image-rejected-none-of-the-signatures-were-accepted--main
|
|
Approving as this is a manual cherrypick of #4380 , which had been approved. /lgtm |
|
@rm3l: you cannot LGTM your own PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
e1efbcd
into
redhat-developer:main



Description
Manual cherry-pick of #4380 (comment) into
mainbecause of conflicts.This contains a specific identity mapping for pulls against
registry.access.redhat.com/rhdh.For some reason, Skopeo would fail otherwise with
Source image rejected: None of the signatures were accepted.Which issue(s) does this PR fix
PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer
See RHDHBUGS-2799 for more context.