Skip to content
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

Consider setting iptables to false in docker daemon.json on the Vulnbox #73

Open
ldruschk opened this issue Jul 21, 2024 · 2 comments
Open
Labels
refactoring Improve/re-create existing features

Comments

@ldruschk
Copy link
Member

During Enowars 8, while everything was working as expected w.r.t Docker networking on the vulnboxes, we did not actually understand why in some cases. Thus we should evaluate whether we can simply set iptables to false and let the docker-proxy handle everything to get rid of the complexity related to Docker iptables

@ldruschk ldruschk added enhancement New feature or request refactoring Improve/re-create existing features and removed enhancement New feature or request labels Jul 21, 2024
@Trolldemorted
Copy link
Member

Reference at https://docs.docker.com/reference/cli/dockerd/ says

Be aware that disabling this option requires you to manually add iptables rules to expose container ports. If you prevent Docker from adding iptables rules, Docker also doesn't add IP masquerading rules, even if you set --ip-masq to true. Without IP masquerading rules, Docker containers can't connect to external hosts or the internet when using network other than default bridge.

@ldruschk
Copy link
Member Author

It should still work due to the docker-proxy process, bur the documentation for that is really lacking. The only thing that should break are connections between containers which are not connected to the same bridge, but that should not be a problem but instead even desirable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Improve/re-create existing features
Projects
Status: No status
Development

No branches or pull requests

2 participants