Which command reveals the port mapping for a container?

Which command reveals the port mapping for a container?

• A. sudo podman inspect <container name>
• B. sudo podman ps -a
• C. sudo podman port -l <container name>
• D. sudo podman port <container name>

Answer: (D)

Port mappings describe how host ports are bound to container ports, so the most direct way to reveal them is to query those published ports with the port subcommand. Running the port command followed by the container identifier asks Podman to display the host-to-container port bindings exactly as they’re exposed, making it the quickest and clearest method to see what ports are mapped. For example, if a container named myapp exposes 80/tcp and 443/tcp and these are published to host ports 8080 and 8443, the command would show mappings like 0.0.0.0:8080->80/tcp and 0.0.0.0:8443->443/tcp. Other commands aren’t as focused on port mappings: inspecting a container shows broader details, including ports, but it’s more verbose; listing containers won’t show mappings at all; and using an incorrect option with port won’t provide the needed information.

Port mappings describe how host ports are bound to container ports, so the most direct way to reveal them is to query those published ports with the port subcommand. Running the port command followed by the container identifier asks Podman to display the host-to-container port bindings exactly as they’re exposed, making it the quickest and clearest method to see what ports are mapped. For example, if a container named myapp exposes 80/tcp and 443/tcp and these are published to host ports 8080 and 8443, the command would show mappings like 0.0.0.0:8080->80/tcp and 0.0.0.0:8443->443/tcp. Other commands aren’t as focused on port mappings: inspecting a container shows broader details, including ports, but it’s more verbose; listing containers won’t show mappings at all; and using an incorrect option with port won’t provide the needed information.