10 ms·
Because you want containers to be able to allocate ports that are already in use on your host. Or at least you don't want that to be a source of errors.
by sascha_sl 4y ago
Because you want containers to be able to allocate ports that are already in use on your host. Or at least you don't want that to be a source of errors.
- sbrivio 4y agoOn top of that, you usually want to isolate the container workload with an observable network abstraction instead of granting it full (albeit non-root) access to host network facilities (including sockets). See https://medium.com/nttlabs/dont-use-host-network-namespace-f548aeeef575 https://medium.com/nttlabs/dont-use-host-network-namespace-f... for just an example of what can go wrong otherwise.