Replies: 3 comments 1 reply
-
Output:
|
Beta Was this translation helpful? Give feedback.
-
By changing the bind address of the application inside the container from |
Beta Was this translation helpful? Give feedback.
-
It seems to be fixed in Podman 5.2.2 (for example in Fedora 40), where Pasta is used for port mapping. Application can listen on localhost and Podman can map it to whatever with -p 0.0.0.0:8080:8080 . Meanwhile I'm using ENV variable, which is changing application to listen everywhere and it fixes Podman 4.9.x port mapping. |
Beta Was this translation helpful? Give feedback.
-
Issue Description
Seeing
Connection reset by peer
when trying to connect to application inside container.Steps to reproduce the issue
Steps to reproduce the issue
1.
2.
3.
Describe the results you received
Describe the results you expected
I expected the published port to be routed to my application and return
OK
as it does inside the container.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Hetzner VM using Fedora 38
Additional information
Freshly installed system.
Beta Was this translation helpful? Give feedback.
All reactions