WolfLink@sh.itjust.works to linuxmemes@lemmy.world · 19 hours agoEvery time I use podmansh.itjust.worksimagemessage-square134fedilinkarrow-up1403arrow-down129
arrow-up1374arrow-down1imageEvery time I use podmansh.itjust.worksWolfLink@sh.itjust.works to linuxmemes@lemmy.world · 19 hours agomessage-square134fedilink
minus-squareWolfLink@sh.itjust.worksOPlinkfedilinkarrow-up7·6 hours agoI literally yesterday dealt with that. There’s an option to just turn off Docker’s firewall manipulation so you can do it manually.
minus-squareRamenator@lemmy.worldlinkfedilinkarrow-up3·2 hours agoI had the same issue, but I just added my plain iptables rules to the DOCKER-USER table, which worked fine
minus-squareWolfLink@sh.itjust.worksOPlinkfedilinkarrow-up1·41 minutes agohttps://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
I literally yesterday dealt with that. There’s an option to just turn off Docker’s firewall manipulation so you can do it manually.
I had the same issue, but I just added my plain iptables rules to the DOCKER-USER table, which worked fine
Please elaborate…
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