• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question How to block external connections into Docker container

Domm

New Pleskian
When you create a Docker container through Plesk and that container has port mappings, then the host ports are automatically opened to the external network.

For example, if you create a MySQL container, and it has the port mapping 32768:3306, then port 32768 on the host machine is implicitly opened to the external network. This means people can attempt to connect to the MySQL server within the container.

I haven't been able to block this using Plesk firewall.

Can anyone suggest a way of securing Docker containers within Plesk, so that they are not just open to the world?
 
Back
Top