-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Podman Network not being able to reach Host (Outbound Connectivity) #25093
Comments
Outbound ConnectivityHost View ( Container View ( Inbound ConnectivityHost View ( Container View ( Hypothesis ?I'd say Routing it's completely broken ... |
Outbound Connectivity in PCAP Format Filtered (TCP 443)Host View ( capture_host_docker-local-mirror-registry_outbound_traffic.zip Container View ( capture_docker-local-mirror-registry_outbound_traffic_port_443.zip Inbound Connectivity in PCAP Format Filtered (TCP 443)Host View ( capture_host_traefik_inbound_traffic.zip Container View ( |
Now you can upgrade to passt-0^20250121.g4f2c8e7-2.fc41 by the way, but I don't think it's going to fix your issue. |
Did you try to reboot? My the rootless netns somehow is a broken/weird state?
So if continue to have problems check if the pasta process is even running and if there are any relevant logs in the journal
That does not look like like the routing setup from a container on the podman network. This looks like the default slirp4netns setup (or possible pasta if you used custom options to make it use the slirp4netns addresses) |
@Luap99: As I said, previously reboot worked (a few Days ago I could "solve" it like this). But this last Time (Yesterday basically) I rebooted like 5 Times and nothing changed unfortunately 😞 |
Container Addresses
Container Routes
Podman Networks
Overall Host Addresses
Pasta Processes
The only weird thing is that I do NOT know why it shows up together with the Container Addresses / Routes. |
Weird ... after upgrade to
|
How do the routes look on the host, one thing to note is that pasta picks the host interface with a default route by default but if there are no default routes or multiple ones then the outcome might not strictly be deterministic. Based on your ip addr output we can see that pasta picked When you did the address/route dump it was in a state where it didn't work? Because that all looks totally valid, the routes seems to be there so a We did has some netavark issues with nftables (new as of f41), we leaked port forwarding rules (and still are in same cases containers/netavark#1160) but that should not matter for outgoing traffic. You can check |
The
Your last Commands that I posted in my Previous Message I run this Evening. This Morning it was NOT working ( No clue if BEFORE I ran these latest Commands it was working or not. I mean ... why should it just start working when it was giving issues from yesterday morning to this morning at least ? Concerning This is the Output
|
Issue Description
In the Last few Days (at least), I experienced some Connectivity Issues in my Docker Local Mirror, which essentially consists of the Following Containers:
docker.io/registry:latest
docker.io/cesanta/docker_auth:latest
In the
traefik
Reverse Proxy Logs I can see the following Message:And indeed I CANNOT
ping
/curl
/etc the Host IP (or the Host upstream Gateway192.168.1.1
for that Matter) from within thetraefik
Container or any of theregistry
ordocker_auth
Containers connected to thetraefik
Network.See "Additional information" for the
compose.yml
Files.Steps to reproduce the issue
Unsure since it occurred after a long period of working correctly 😞.
Describe the results you received
HTTP Page does NOT display at all ("white") in Firefox.
traefik
Logs show:Trying to access the Service from within a Container running in the
podman
Network:The same Result for
curl
can be obtained by executing the same Command directly on the Host.I cannot even run
apk add curl
from eithertraefik
nordocker-local-mirror-registry
Container, so I'd say ALL containers on thetraefik
Network are affected.Container(s?) on the
podman
Network seem to be fine with regards to Outbound Connectivity and I can (getting an error because the converter doesn't reply) curl the docker mirrorPacket Capture OUTBOUND:
docker-local-registry-mirror
Container ->apk update
Servers attached.Packet_Capture_OUTBOUND_from_docker-local-registry-mirror_Container_to_apk_update_Servers.txt
Packet Capture Inbound: Desktop Firefox ->
traefik
Container attached.Packet_Capture_INBOUND_from_Desktop_Firefox_to_traefik_Container.txt
Describe the results you expected
Traefik simply forwards the Connection to the
docker-auth
Container for validating Credentials.ping
/curl
/ etc of192.168.8.15
IP Address (HOST IP Address) should have been successfull.podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Podman Networks on this Host
Details of
podman
Network:Details of
traefik
Network:Additional information
Local Docker Mirror
compose.yml
File:Entrypoint:
docker.io/traefik:v3.2
Its
compose.yml
File:The text was updated successfully, but these errors were encountered: