• 0 Posts
  • 100 Comments
Joined 1 年前
cake
Cake day: 2024年6月21日

help-circle


  • You’ve likely given it full control to whatever storage you’ve mounted in the container anyway, unless you’ve given it the :ro flag, which in that case would operate the same regardless of networking mode. If someone gains access to your internal host, you have bigger problems. Some things just play better under host mode and all bridged mode is doing is creating a virtual switch on your host and passing allowed traffic through it at a base level. The best way to protect is by running a load balancer in a DMZ and proxying all of the traffic through it which is how I have my instance running. I funnel everything external --> TCP\UDP 443 in DMZ vlan load balancer --> internal LAN IP:docker port. I run a mix of host network or bridged mode depending on the container.













  • I’ve not heard of mail in a box but I’m using Mailcow myself. They have a full docker compose and update script that will tear down and upgrade the stack itself. Been using it for years with little issue.

    It’s a good thing you have a mail forwarded already as you risk getting immediately grey listed without one for outgoing mail. I’m using SMTP2Go myself and it works great. They have a free tier that works for very little volume outbound. I may need to see about moving to ImprovMX if it makes sense to do so.

    My use case is basically for internal system alerts and testing for work mainly. I don’t want to rely too heavily on my internal mail server because if it blows up for some reason, I don’t want to have important information in it that could be costly (time consuming) to recover.