3 ms·
There are some things you need to know though. For example most devs today "know" Docker, but very few realize that it opens the exposed ports on the host firew
by worksonmine 3y ago
There are some things you need to know though. For example most devs today "know" Docker, but very few realize that it opens the exposed ports on the host firewall. Exposing a port for another service to access internally is intuitively safe, until you look at the box and realize that same port was opened to the internet. Convenient thought the docker devs, but touching something so important without feedback is reckless. That's an abstraction that absolutely shouldn't be there, too many devs don't RTFM.