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.

This is an RFE from talking with customers at Container Con.


During Container Con, Docker presented the ability to sign docker images and thus allow a user to trust that an image is valid. In this same vein rkt demonstrated similar capabilities and spoke about how they are looking to expand this to allow/disallow certain actions based on the level of trust given to a particular key.

Docker should provide this kind of control as well. 

For example, if an image was signed with key A that the user trusts for network operations, but not for storage operations then docker could be configured to refuse to start a container if the user was trying to volume-mount something into the container. However, if the image was signed with key B that the user "trusts more", then docker would allow the volume-mount.

Ok we don't see a way to do this, and have no plans to implement it.