-
Notifications
You must be signed in to change notification settings - Fork 328
-
Notifications
You must be signed in to change notification settings - Fork 328
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
Warn users of postgress exposure and ufw override #947
Comments
Just a word of warning. Turning off IP tables in Docker caused my deployment containers to lose connectivity. |
This solution appears to be working for me. It stops the ports Docker containers are binding to from being publicly available and allows me to expose just what I need using UFW To Fix The Docker and UFW Security Flaw Without Disabling Iptables. |
Instead of using the |
Added to FAQ @ianhe8x |
This is more of a suggestion than an issue
Below points can be added in the documentation as a warning.
1 - Warn the users to change the password in postgress and port /do not keep the default password for the same in docker-compose
2 - Firewall rules are bypassed by docker containers by default so add these commands or a note to notify users
To disable one can set
in /etc/docker/daemon.json
echo "DOCKER_OPTS=\"--iptables=false\"" >> /etc/default/docker
restart docker service
service docker restart
The text was updated successfully, but these errors were encountered: