3 ms·
> the complexity of using [UNIX sockets] in containerized environments made them less attractive than TCP Huh, I would think UNIX sockets would be easier; sinc
by kelnos 3y ago
> the complexity of using [UNIX sockets] in containerized environments made them less attractive than TCP
Huh, I would think UNIX sockets would be easier; since sharing the socket between the host and a container (or between containers) is as simple as mounting a volume in the container and setting permissions on the socket appropriately.
Using TCP means dealing with iptables and seems... less fun. I easily run into cases where the host's iptables firewall interferes with what Docker wants to do with iptables such that it takes hours just to get simple things working properly.
- Galanwe 3y agoThis. Especially, docker does a lot of magic dynamically adding/removing iptables rules, which is already a nightmare to manage, so you really want to avoid dealing with more.
- dathinab 3y agoit's an issue of tooling I thing, through dependent on what containerized runtimes e.g. in docker you can use -p to publish ports of containers on the host, this trends to get much more messy less ad-hoc usage where you want to publish them between containers, but docker-compose and similar handle all that for you the benefit of that is this works with the container rubbing using a vm or a namespace created by you or root and it even can work if the container is run somewhere else with pipes you have to volume mount them and do so in a way which works with whatever docker uses to do so, which if you then also mix in docker on windows or Mac can get a bit annoying through of we speak about containerization for apps e.g. using snap/flatpack pipes should work just fine and in the end they are the most common used for cross process communication on the same system, i.e. use case wher you don't have to worry about vms and cross os communication