Open p5 opened 19 hours ago
You say root and rootless but your video shows rootless only and podman is not failing pasta is and we do not use pasta as root at all so I do not see how root would fail at all. In particular root doesn't care about the external interfaces with its bridge + NAT (MASQUERADE) setup which should always run fine.
The pasta error means it failed to copy your host routes into the container so please provide the full routes when this happens ip route
because this is bug. Because pasta fails if there is no external interface not found but it should generally not fail adding routes.
ps: please copy pasta the error message so it can be indexed for the search
I did have issues with rootful networking when I tried this out (both being "Network Unreachable" errors), but you must be right - it's probably some other transient issue. I must have misunderstood them as the same issue.
When trying to reproduce today, rootful works fine whereas I am still able to replicate with rootless.
The error depends on what I am trying to do in the container.
Most of the time, it's Network is unreachable
.
And digging around in the debug Podman logs, I can see the following, though I am unsure whether the conmon error is related:
DEBU[0000] pasta arguments: --config-net --dns-forward 169.254.0.1 -t none -u none -T none -U none --no-map-gw --quiet --netns /run/user/1000/netns/netns-b1acbc49-50c0-7337-c86b-e4a263692f5c
INFO[0000] pasta logged warnings: "Couldn't get any nameserver address\n"
---
[conmon:d]: failed to write to /proc/self/oom_score_adj: Permission denied
IP routes:
❯ ip route
default via 192.168.0.1 dev eno1 proto dhcp src 192.168.0.177 metric 100
default via 192.168.0.1 dev wlp9s0 proto dhcp src 192.168.0.26 metric 600
192.168.0.0/24 dev wlp9s0 proto kernel scope link src 192.168.0.26 metric 600
Full log:
Issue Description
Very strange one. When I am on my system, and I switch between WiFi and Ethernet adapters, Podman occasionally refuses to connect to any networks. This happens with both rootful and rootless containers, and also causes errors during builds.
In the below video, you can see:
https://github.com/user-attachments/assets/c6ff43ad-8efe-4ae9-b8c6-cfdfdf89425b
Now, this could be a Linux bug. But I thought I'd start here and see what you all think of it. I'm hoping this is easily reproducible since I could not find any relevant logs.
I would understand (and possibly expect) an error if the same container failed to seamlessly switch between NICs, but this is happening when I create completely different containers.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
See above video
Describe the results you expected
Podman to figure out the right network to use when spinning up a new container on a different network interface.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
I am able to reproduce this roughly 1 in 3 times I switch from two enabled NICs to one. If I wait for a couple minutes after switching from two to one adapter, the same still happens, so it doesn't seem like anything is happening in the background.