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.
Bug 1815170 - podman-docker seems packed with wrong path of podman manual.
Summary: podman-docker seems packed with wrong path of podman manual.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-19 17:10 UTC by Kirby Zhou
Modified: 2020-07-21 15:32 UTC (History)
9 users (show)

Fixed In Version: podman-1.9.0 and newer
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-21 15:31:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:3053 0 None None None 2020-07-21 15:32:38 UTC

Description Kirby Zhou 2020-03-19 17:10:51 UTC
Description of problem:

podman-docker seems packed with wrong path of podman manual.

Version-Release number of selected component (if applicable):

podman-docker-1.6.4-2.module_el8.1.0+272+3e64ee36.noarch


How reproducible:

100%

Steps to Reproduce:
1. dnf install podman-docker
2. man docker

Actual results:

man: can't open /usr/share/man/man1/./docs/build/man/podman.1: No such file or directory
No manual entry for docker


Expected results:

Show the man of podman.

Additional info:

~]$ zcat /usr/share/man/man1/docker.1.gz
.so man1/./docs/build/man/podman.1

Comment 1 Daniel Walsh 2020-03-19 18:05:30 UTC
PR To fix in master

https://github.com/containers/libpod/pull/5559

Comment 2 Tom Sweeney 2020-06-05 16:44:21 UTC
Setting to Post and assigning to Jindrich in case there's any packaging needs.  This was fixed in Podman v1.9.0 and later versions.

Comment 7 Joy Pu 2020-06-16 13:26:15 UTC
Test with podman-1.9.3-2.module+el8.2.1+6867+366c07d6.x86_64. And now the command "man docker" can find the podman manual as expect. So set this to verified.

Comment 8 Kirby Zhou 2020-06-30 08:20:52 UTC
Do(In reply to Joy Pu from comment #7)
> Test with podman-1.9.3-2.module+el8.2.1+6867+366c07d6.x86_64. And now the
> command "man docker" can find the podman manual as expect. So set this to
> verified.

Is podman-1.9.3 availabe in RHEL-8.2?
I can only find 1.6.4-10.

Comment 9 Matthew Heon 2020-06-30 13:20:13 UTC
1.9.3 is available as part of the RHEL 8.2.1 release

Comment 11 errata-xmlrpc 2020-07-21 15:31:55 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-2020:3053


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