-
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
Rootless Podman networking not working on boot until after removing user rootless-netns
folder and restarting service
#22637
Comments
Is only dns not working or no networking at all? Do you have a aadvark-dns process running? |
Correct, no networking until removal of
aardvark-dns is running:
Unit logs don't reveal much apart from connection errors to external networks.
Please let me know what other logs I can provide. |
rootless-netns
folder and restartingrootless-netns
folder and restarting service
If the issue is networking then I strongly suspect this to be a duplicate of #22197, I suggest you try one of the workarounds there |
Ok, as per #22197, I've added my own user
And configured all my quadlets to This is definitely a workaround, and not a true solution, so up to you @Luap99 whether to close this issue and track a solution in #22197 or otherwise. Nevertheless, thank you for pointing to that issue, because a workaround is better than having no way around functional services except manual intervention, especially when my server auto-updates and restarts. |
Thanks, I close it as dup then |
Issue Description
On Fedora 40 server using Podman 5, I have a few rootless quadlets set to run at boot. I create individual networks for different services so that services can communicate with their dependencies (e.g. WordPress and a MariaDB instance). The different containers and networks are symlinked in
~/.config/containers/systemd/
, and my container user hasLinger=yes
set, so they run at boot.An example network looks like this:
wordpress.network
While the pods startup without issue, DNS resolution does not work (as evidenced by
podman exec -u root wordpress nslookup google.com
) until I remove/run/user/1000/containers/networks/rootless-netns/
and restart the service.podman version:
rpm -q podman:
podman-5.0.2-1.fc40.x86_64
Steps to reproduce the issue
Steps to reproduce the issue
podman exec -u root [service] nslookup google.com
Describe the results you received
No DNS resolution
Describe the results you expected
DNS records successfully returned
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Commodity x86 machine. I use systemd-networkd with systemd-networkd-wait-online enabled.
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: