Bug 2020301 - Unable to pull UBI 9 images from non-RHEL
Summary: Unable to pull UBI 9 images from non-RHEL
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: doc-Release_Notes-8-en-US
Version: 8.5
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 8.7
Assignee: Lucie Vařáková
QA Contact:
Gabriela Nečasová
URL:
Whiteboard:
Depends On: 2020026 2094015
Blocks: 2022796
TreeView+ depends on / blocked
 
Reported: 2021-11-04 14:42 UTC by Derrick Ornelas
Modified: 2022-11-10 06:50 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
.Container images signed with a Beta GPG key can now be pulled Previously, when you pulled RHEL Beta container images, Podman failed with the error message: `Error: Source image rejected: None of the signatures were accepted`. The images failed to be pulled due to current builds being configured to not trust the RHEL Beta GPG keys by default. With this update, the `/etc/containers/policy.json` file supports a new `keyPaths` field which accepts a list of files containing the trusted keys. Because of this, the container images signed with GA and Beta GPG keys are now accepted in the default configuration.
Clone Of: 2020026
: 2022796 (view as bug list)
Environment:
Last Closed: 2022-11-10 06:50:19 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-101850 0 None None None 2021-11-05 11:35:11 UTC
Red Hat Knowledge Base (Solution) 6487081 0 None None None 2021-11-05 17:08:51 UTC

Comment 3 Daniel Walsh 2021-11-05 17:43:20 UTC
Why?  Why would we make everything less secure, just to allow users to install beta software.  Can't we just enhance the tool to allow the beta images?

Comment 26 RHEL Program Management 2022-10-12 18:47:12 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Comment 29 RHEL Program Management 2022-10-12 18:49:40 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.