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 2090166 - Error in man podman run manual
Summary: Error in man podman run manual
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Joy Pu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-25 09:29 UTC by Krishnakumar
Modified: 2023-05-16 09:01 UTC (History)
14 users (show)

Fixed In Version: podman-4.3.1-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-16 08:18:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 13929 0 None Merged slirp4netns: actually make ipv6 default 2022-08-05 12:19:06 UTC
Github containers podman pull 15790 0 None Merged [CI:DOCS] improve slirp4netns allow_host_loopback docs 2022-09-23 11:28:31 UTC
Red Hat Issue Tracker RHELPLAN-123304 0 None None None 2022-05-25 09:34:47 UTC
Red Hat Product Errata RHSA-2023:2758 0 None None None 2023-05-16 08:38:51 UTC

Description Krishnakumar 2022-05-25 09:29:08 UTC 
Description of problem:

What problem/issue/behavior are you having trouble with?  What do you expect to see?
Hello,

In the podman-run man page there is an error about the host.containers.internal address. The sentence "10.0.2.2, which is added to /etc/hosts as host.containers.internal for your convenience" is false since podman 4.0.0 (see https://github.com/containers/podman/issues/12000)

Also 10.0.2.2 is not necessarily the loopback ip if the cidr is customized with the cidr option.

Could you fix the doc ?

Thanks,

What is the business impact? Please also provide timeframe information.
manual can't be trusted


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

podman 4


How reproducible:

man podman run

Steps to Reproduce:
1. 
2.
3.

Actual results:

      additional options:
         - allow_host_loopback=true|false: Allow the slirp4netns to reach the host loopback IP (10.0.2.2, which is added to /etc/hosts
       as host.containers.internal for your convenience). Default is false.
         - mtu=MTU: Specify the MTU to use for this network. (Default is 65520).


Expected results:

IP address has to be corrected in manual page.

Additional info:
Comment 1 Tom Sweeney 2022-05-25 13:01:26 UTC 
@kmarutha I'm a little confused by where the man page that you're referring to is located?  This BZ is reported against RHEL 8.5 and that should be Podman v3.4, and I think that entry holds still in that instance.
The man page in RHEL 8.6 has been corrected AFAIK, but I could be wrong.
Comment 8 Tom Sweeney 2022-05-27 21:22:40 UTC 
@jke also, I'm not seeing the message from the description from this BZ.   "10.0.2.2, which is added to /etc/hosts as host.containers.internal for your convenience".  Is that still in play, or is it just the allow_host_loopback?

@pholzing can  you PTAL and adjust as necessary, or let me know what needs to be adjusted?
Comment 9 Paul Holzinger 2022-05-30 12:17:46 UTC 
The `, which is added to /etc/hosts as host.containers.internal for your convenience` part is definitely not correct and was already removed upstream.
Comment 22 Paul Holzinger 2022-09-14 09:00:30 UTC 
PR: https://github.com/containers/podman/pull/15790
Comment 23 Tom Sweeney 2022-09-14 12:50:19 UTC 
Paul, thanks for the wording change.  @gnecasov please take note, we may need a RHEL documentation change I think.  Paul's wording works for me.

`podman create` man page:

**allow_host_loopback=true|false**: Allow slirp4netns to reach the host loopback IP (default is 10.0.2.2 or the second IP from slirp4netns cidr subnet when changed, see the cidr option below). The default is false.
Comment 24 Gabriela Nečasová 2022-09-14 13:02:45 UTC 
Tom, thank you, I will make a note.
Comment 25 Joy Pu 2022-09-14 13:33:05 UTC 
Thanks Paul and Tom, based on the discuss set the bug back to assign.
Comment 35 Joy Pu 2022-12-16 15:25:22 UTC 
Checked with podman-4.3.1-1.module+el8.8.0+17458+77eef5df.x86_64 in the podman run manual the doc is already updated:
         -  allow_host_loopback=true|false:  Allow  slirp4netns  to  reach  the  host  loopback  IP (default is 10.0.2.2 or the second IP from
       slirp4netns cidr subnet when changed, see the cidr option below). The default is false.
         - mtu=MTU: Specify the MTU to use for this network. (Default is 65520).
         - cidr=CIDR: Specify ip range to use for this network. (Default is 10.0.2.0/24).
So move this to verified.
Comment 37 errata-xmlrpc 2023-05-16 08:18:40 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 (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), 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-2023:2758
Comment 38 errata-xmlrpc 2023-05-16 08:38:40 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 (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), 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-2023:2758
Note You need to log in before you can comment on or make changes to this bug.