https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/building_running_and_managing_containers/assembly_communicating-among-containers_building-running-and-managing-containers#con_the-network-modes-and-layers_assembly_communicating-among-containers

 
Describe your experience on docs.redhat.com:

• Neither satisfied nor dissatisfied
   
   Why did you visit this page today?
• Find out how to complete a task
   
  . What is the feedback about?
• Content
   
    Please share any additional feedback that could help us improve your experience: 
  Hello!

I was reading through this section:

https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/building_running_and_managing_containers/assembly_communicating-among-containers_building-running-and-managing-containers#proc_communicating-between-containers-using-port-mapping_assembly_communicating-among-containers

Yes, I was using CentOS 9 (fully updated with podman-5.3.1-1.el9.x86_64 but that should not matter) and found these bugs in the docs:

In 11.7. point 4, this is the output I got:

—

1. podman ps

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

ff0f5f09920a registry.access.redhat.com/ubi9/httpd-24:latest /usr/bin/run-http... 16 seconds ago Up 13 seconds 8080/tcp, 8443/tcp web1

2145e373635e registry.access.redhat.com/ubi9/httpd-24:latest /usr/bin/run-http... 10 seconds ago Up 9 seconds 0.0.0.0:41501->8443/tcp, 0.0.0.0:41971->8080/tcp web2

dcc39c2e6df2 registry.access.redhat.com/ubi9/httpd-24:latest /usr/bin/run-http... 5 seconds ago Up 4 seconds 0.0.0.0:9090->80/tcp, 8080/tcp, 8443/tcp web3

—

In 11.7. point 8, you are mentioning same IP address for web3 10.88.0.14 as in point 6 for web1 which is confusing.

In 11.7. point 3 you are using "-p 9090:80", but that leads to command in point 8 (with IP address fixed) to fail. I suppose correct option in point 3 is "-p 9090:8080".

In 11.6. point 1 to get a device name, I had to use grep like this:

—

1. podman network inspect podman | grep network_interface

"network_interface": "podman0",

—

as this was not showing output shown in the doc:

—

1. podman network inspect podman | grep bridge

"driver": "bridge",

—