When using podman as a backend for docker cli docker ps
fails to show port-forwarding correctly
#22367
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
remote
Problem is in podman-remote
Issue Description
I have podman and podman desktop installed on my ARM MacOS.
I am still using the
docker
CLI tool although the backend is podman-desktop, and I got confused today whendocker ps
reported an incorrect value for a specific container's ports. When I usepodman ps
though it shows the ports correctly, and if I try to connect the the host port it works fine, so it is just a visualization problem.Steps to reproduce the issue
I prepared a small reproducible example:
If you look at the "ports" section of both outputs you will see that the
podman
CLI is correctly displaying0.0.0.0:9080->80/tcp
, butdocker
is only displaying80/tcp
, which I think is not the intended behavior.I did notice one interesting thing though, if I include a source IP on the port pattern, e.g.
::1:9080:80
instead of just9080:80
the docker CLI does show the correct value, e.g.:Describe the results you received
docker cli shows an incorrect value for the port field
Describe the results you expected
I expected the output of
docker ps
to match the output ofpodman ps
when displaying which host ports are forwarded to each container.podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Its an MacBook Pro M1 running Sonoma 14.3.1 (23D60)
Additional information
No response
The text was updated successfully, but these errors were encountered: