Hacker News Reader

Even VM will need an IP-address-space shared with the host so you can access them.

That’s not a docker/container problem.

Btw, you‘re able to configure the Ip-space to use by passing an argument to the daemon or change it in daemon.json.

Most VM hypervisors allow the creation of virtual networks that are only visible to the VMs on the network, not to the host. The connection of the host to the virtual network is an extra step involving a TAP driver that translates between the host OS and the hypervisor process. Obviously, the virtual networks themselves, when the TAP driver is not loaded, are not going to mess with the host's routing configuration like a (normal, rootful) docker deployment would, by virtue of being invisible to the host's networking stack.

Also, yes, it is a docker problem in particular. Linux has a solution for virtualizing networking for a subset of processes only: network namespaces. Docker doesn't use them by default, but can be taught to do so with the rootless kit. All rootless container engines use them by default.

ssh user@fe80::xxx%tapvm

as long as ipv6 link local are not disabled the fe80 addresses work nicely :)

Reply on news.ycombinator.com