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.
+++ This bug was initially created as a clone of Bug #1515783 +++
Description of problem:
While investigating why my automation stopped working, I found out that the format of /etc/containers/registries.conf has changed recently. No worries, there used to be a registries(1) man page which explained the mechanism.
Except, the man page packaged with atomic-registries-1.20.1-1.fc26.x86_64 does not work.
Version-Release number of selected component (if applicable):
atomic-registries-1.20.1-1.fc26.x86_64
How reproducible:
Deterministic.
Steps to Reproduce:
1. man registries
Actual results:
# man registries
man: warning: /usr/share/man/man1/registries.1.md.gz: ignoring bogus filename
No manual entry for registries
Expected results:
Something like the output with atomic-registries-1.18.1-5.fc26.x86_64:
REGISTRIES(1) May 2017 REGISTRIES(1)
NAME
registries - parses a YAML configuration file for registries
SYNOPSIS
registries [-h|--help] [-i][--input] [-j][--json] [-o][--output]
[-V][--variable]
DESCRIPTION
registries parses a YAML configuration file about registries and has
the ability to output in string or JSON formats. By default, reg‐
istries will put its output to stdout in string format. The output is
primarily for other programs.
Additional info:
--- Additional comment from Brent Baude on 2017-11-21 15:38:50 EST ---
I've built atomic-1.20.1-3 which should fix this. Karma always appreciated.
--- Additional comment from Fedora Update System on 2017-11-21 15:40:38 EST ---
atomic-1.20.1-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f6a5dd1d5e
--- Additional comment from Fedora Update System on 2017-11-21 15:41:17 EST ---
atomic-1.20.1-3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-5260fcff0c
--- Additional comment from Fedora Update System on 2017-11-21 15:41:29 EST ---
atomic-1.19.1-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-d610d267e5
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/RHBA-2017:3365