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.
Description of problem:
We are not having any location for keeping the certificates for private registries such as certs.d at /etc/containers/certs.d location
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 8 Beta
podman-1.0.0-1.git82e8011.module+el8+2696+e59f0461.x86_64
Additional Info :
/etc/containers/ should have a certs.d directory consisting of the registries we are going to incorporate as in docker
As we providing these 3 in regsitries.conf file currently in latest podman :
1. registry.redhat.io
2. quay.io
3. docker.io
Valentin can you look into how this would work with containers/image?
Comment 2Valentin Rothberg
2019-03-01 11:24:02 UTC
(In reply to Daniel Walsh from comment #1)
> Valentin can you look into how this would work with containers/image?
containers/image supports this already (see https://github.com/containers/image/blob/master/docker/docker_client.go#L56). There are two lookup paths, namely `/etc/{containers,docker}/certs.d`, with containers having a higher priority but it's not created by the tools or the packages which aligns with docker's behavior.
`man podman-pull`, for instance, mentions the default path but we could reflect if the text could be more explicit.
We can also add the /etc/containers/certs.d directory to containers-common.
Comment 4Valentin Rothberg
2019-03-01 11:29:59 UTC
(In reply to Daniel Walsh from comment #3)
> We can also add the /etc/containers/certs.d directory to containers-common.
I like the idea. Maybe, we can add a `container-certs.d` manpage on top which can later be cross-referenced in the tools' pages?
Comment 5Valentin Rothberg
2019-03-01 12:24:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:3403