You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't a podman issue (I think), but it'd be good to confirm what the problem is and make it visible. My machine has both docker and podman installed, which had been working fine in Fedora 40.
I upgraded from Fedora 40 to Fedora 41 and rootfull podman containers appeared to lose internet access:
rootless:
podman run --rm -it fedora curl --max-time 5 https://wikipedia.org/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.wikipedia.org/">here</a>.</p>
</body></html>
rootfull:
sudo podman run --rm -it fedora curl --max-time 5 https://wikipedia.org/
curl: (28) Connection timed out after 5002 milliseconds
I found that in Fedora 41 the netavark default has moved to nftables so my theory is the docker iptables config is clobbering things.
Docker appears to set a policy of DROP on the iptables FORWARD chain. If I set the policy to ACCEPT, then rootfull podman has internet access.
sudo iptables -P FORWARD ACCEPT
sudo podman run --rm -it fedora curl --max-time 5 https://wikipedia.org/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.wikipedia.org/">here</a>.</p>
</body></html>
Steps to reproduce the issue
I reproduced this in a fresh VM
Steps to reproduce the issue
Install latest Fedora 41 ISO (I used Fedora-Workstation-Live-x86_64-41-1.4.iso with Gnome Boxes)
now rootfull podman will fail to communicate with the internet:
sudo podman run --rm -it fedora curl -m 5 https://wikipedia.com
curl: (28) Resolving timed out after 5000 milliseconds
Change the iptables FORWARD policy to ACCEPT and rootfull podman has internet access
robeyoun@fedora:~$ sudo iptables -P FORWARD ACCEPT
robeyoun@fedora:~$ sudo podman run --rm -it fedora curl -m 5 https://wikipedia.com
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.22.1</center>
</body>
</html>
Describe the results you received
When docker is installed, rootfull podman doesn't have internet access
Describe the results you expected
The dream would be docker and podman can coexist together out of the box. But given it's about how docker configures things maybe it's just something that could go in docs?
Issue Description
This isn't a podman issue (I think), but it'd be good to confirm what the problem is and make it visible. My machine has both docker and podman installed, which had been working fine in Fedora 40.
I upgraded from Fedora 40 to Fedora 41 and rootfull podman containers appeared to lose internet access:
rootless:
rootfull:
I found that in Fedora 41 the netavark default has moved to nftables so my theory is the docker iptables config is clobbering things.
Docker appears to set a policy of DROP on the iptables FORWARD chain. If I set the policy to ACCEPT, then rootfull podman has internet access.
Steps to reproduce the issue
I reproduced this in a fresh VM
Steps to reproduce the issue
sudo dnf-3 config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo
sudo dnf install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo systemctl start docker
At this point docker should have configured iptables like:
now rootfull podman will fail to communicate with the internet:
Change the iptables FORWARD policy to ACCEPT and rootfull podman has internet access
Describe the results you received
When docker is installed, rootfull podman doesn't have internet access
Describe the results you expected
The dream would be docker and podman can coexist together out of the box. But given it's about how docker configures things maybe it's just something that could go in docs?
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
Yes
Additional environment details
Additional information
No response
The text was updated successfully, but these errors were encountered: