▲ 438 ▼ Every time I use podman (thelemmy.club) submitted 1 day ago by WolfLink@sh.itjust.works to c/linuxmemes@lemmy.world 160 comments fedilink hide all child comments
[–] deathmetal27@lemmy.world 24 points 15 hours ago (2 children) This is why I don't like Docker compared to Podman: permalink fedilink source hideshow 4 child comments replies: [–] xavier666@lemmy.umucat.day 2 points 1 hour ago I may be dumb but I apply the firewall at the router level (OPNsense). That should be fine, right? permalink fedilink source parent [–] WolfLink@sh.itjust.works [S] 8 points 15 hours ago (2 children) I literally yesterday dealt with that. There’s an option to just turn off Docker’s firewall manipulation so you can do it manually. permalink fedilink source parent hideshow 4 child comments replies: [–] Ramenator@lemmy.world 3 points 11 hours ago I had the same issue, but I just added my plain iptables rules to the DOCKER-USER table, which worked fine permalink fedilink source parent [–] theforceofvader1@sh.itjust.works 1 point 13 hours ago (1 child) Please elaborate... permalink fedilink source parent hideshow 2 child comments replies: [–] WolfLink@sh.itjust.works [S] 2 points 10 hours ago https://docs.docker.com/engine/network/packet-filtering-firewalls/#prevent-docker-from-manipulating-firewall-rules Basically put: { iptables: False, Ip6tables: False } In /etc/docker/daemon.json permalink fedilink source parent
[–] xavier666@lemmy.umucat.day 2 points 1 hour ago I may be dumb but I apply the firewall at the router level (OPNsense). That should be fine, right? permalink fedilink source parent
[–] WolfLink@sh.itjust.works [S] 8 points 15 hours ago (2 children) I literally yesterday dealt with that. There’s an option to just turn off Docker’s firewall manipulation so you can do it manually. permalink fedilink source parent hideshow 4 child comments replies: [–] Ramenator@lemmy.world 3 points 11 hours ago I had the same issue, but I just added my plain iptables rules to the DOCKER-USER table, which worked fine permalink fedilink source parent [–] theforceofvader1@sh.itjust.works 1 point 13 hours ago (1 child) Please elaborate... permalink fedilink source parent hideshow 2 child comments replies: [–] WolfLink@sh.itjust.works [S] 2 points 10 hours ago https://docs.docker.com/engine/network/packet-filtering-firewalls/#prevent-docker-from-manipulating-firewall-rules Basically put: { iptables: False, Ip6tables: False } In /etc/docker/daemon.json permalink fedilink source parent
[–] Ramenator@lemmy.world 3 points 11 hours ago I had the same issue, but I just added my plain iptables rules to the DOCKER-USER table, which worked fine permalink fedilink source parent
[–] theforceofvader1@sh.itjust.works 1 point 13 hours ago (1 child) Please elaborate... permalink fedilink source parent hideshow 2 child comments replies: [–] WolfLink@sh.itjust.works [S] 2 points 10 hours ago https://docs.docker.com/engine/network/packet-filtering-firewalls/#prevent-docker-from-manipulating-firewall-rules Basically put: { iptables: False, Ip6tables: False } In /etc/docker/daemon.json permalink fedilink source parent
[–] WolfLink@sh.itjust.works [S] 2 points 10 hours ago https://docs.docker.com/engine/network/packet-filtering-firewalls/#prevent-docker-from-manipulating-firewall-rules Basically put: { iptables: False, Ip6tables: False } In /etc/docker/daemon.json permalink fedilink source parent