slirp4netns
works but pasta
not
#25497
Answered
by
Luap99
kingwingfly
asked this question in
Q&A
-
podman --version
podman version 5.4.0 If I use podman run --name server -itd <...> --network slirp4netns -p 8081:8081 --replace server Then curl http://localhost:8081
{"ok":false,"error_code":404,"description":"Not Found"} However, if I change to podman run --name server -itd <...> -p 8081:8081 --replace server
# default pasta I got: curl http://localhost:8081
curl: (56) Recv failure: Connection reset by peer If anybody knows the solution or needs more info, please give a hand 🙏 It's so kind of you! |
Beta Was this translation helpful? Give feedback.
Answered by
Luap99
Mar 6, 2025
Replies: 1 comment 1 reply
-
What is the server, can you share the image? Is it possible that localhost connect to |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
kingwingfly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the server, can you share the image?
Have you check what ports pasta bound (
ss -tlpn
) on the host?Is it possible that localhost connect to
::1
not127.0.0.1
and you service in the container only listens on ipv4? Maybe just try to curl 127.0.0.1 directly.