-
Notifications
You must be signed in to change notification settings - Fork 88
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
CHAIN_ADD failed (No such file or directory): chain PREROUTING #62
Comments
Hmm, do you have any idea why this happens?(I don't have a windows machine) |
@xehonk do you use docker with wsl2 enabled? https://learn.microsoft.com/en-us/windows/wsl/tutorials/wsl-containers |
@qoomon Sorry, I don't have access to the affected machine until next week. I'll find out then. |
So, here's the update:
I also verified this on another computer running windows. Same result. |
probably it's due to iptables-nft change in alpine version 3.19.0 https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.19.0 |
Maybe adding following lines to entrypoint.sh before iptable commands could help modprobe ip_tables && echo $_ >> /etc/modules
modprobe iptable_nat && echo $_ >> /etc/modules
modprobe iptable_filter && echo $_ >> /etc/modules |
I have not tried this on windows, but even on linux there's this error with your suggested change. I do not think the alpine base image includes these loadable modules. modprobe: can't change directory to '/lib/modules': No such file or directory |
I'll will try to migrate to nftables maybe this will work |
feel free to try this branch https://github.com/qoomon/docker-host/tree/feature/migrate-to-nftables |
hmm i have no clue what's the reason, or why the iptables legacy solution works |
@xehonk I switched to iptables-legacy. Feel free to try version 3.3.0 |
In the new release (3.1.4) there is an error, which prevents the container from starting. Only happened on a windows host, not on a linux host.
iptables v1.8.10 (nf_tables): CHAIN_ADD failed (No such file or directory): chain PREROUTING
The text was updated successfully, but these errors were encountered: