-
Notifications
You must be signed in to change notification settings - Fork 408
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
iptables migration to nftables on debian #9
Comments
Hi @pniederlag, Thanks for the new information. Could you issue a pull request to merge your work into this project? Thank you! BTW, I just returned back to China from Germany yesterday ^_^ I was quite busy with our client in Germany in the past three weeks. |
I doubt this is a general solution as I'd not expect to be iptables-legacy to exist everywhere. Anyway this is the unified diff
|
Digging further into the matter it even turns out switching to iptables-legacy does not make sense at all. docker 18.09.4 has reverted the "hack" for iptables-legacy on debian. Its seems like some other problem was fixed instead to make docker work happily with iptables-nft (which is the suggested iptables API for nfttables). Details: docker-archive/engine#169 If you are on debian/buster:
enjoy |
Thanks for your information |
Recently debian has switched to nftables by defaut (buster/unstable)
Debian is using builtin alternatives system to provide iptables command by either iptables-nft or iptables-legacy.
Upstream docker/libnetwork has incorporated this by updating libnetwork to use 'iptables-legacy' if available moby/libnetwork#2285
I updated ufw-docker to use iptables-legacy and it seems to work. Otherwise it would not detect the DOCKER related chains as they'd be hidden in iptables-nft.
More on the docker story in regards to iptables/nftables can be found on this issue: moby/moby#26824 it seems distros are slowly picking up nftables causing docker some troubles ....
The text was updated successfully, but these errors were encountered: