Bug 2090166
| Summary: | Error in man podman run manual | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Krishnakumar <kmarutha> |
| Component: | podman | Assignee: | Jindrich Novy <jnovy> |
| Status: | CLOSED ERRATA | QA Contact: | Joy Pu <ypu> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.5 | CC: | bbaude, dwalsh, gnecasov, jke, jligon, jnovy, lsm5, mheon, pholzing, pthomas, snangare, tsweeney, umohnani, ypu |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | podman-4.3.1-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-16 08:18:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Krishnakumar
2022-05-25 09:29:08 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. @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? The `, which is added to /etc/hosts as host.containers.internal for your convenience` part is definitely not correct and was already removed upstream. 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. Tom, thank you, I will make a note. Thanks Paul and Tom, based on the discuss set the bug back to assign. 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.
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 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 |