Hacker News new | past | comments | ask | show | jobs | submit login

The simplest solution of all, as far as I can tell, is to add a new virtual interface to the host (all hypervisors provide this functionality; or use macvlan on bare metal) and assign it to the container after obtaining layer 3 information about it (DHCP, static addressing, whatever). Then you don't have to worry about the complexity of overlay networks or NAT.

What's the objection to this?




That's a great idea unless you run out of addresses or your cloud provider only gives you 8 per VM or you want multitenancy etc.


Embrace IPv6 =)


Under what realistic scenarios would you want that many addressable containers on a host?


Containers can add up fast with microservices and sidecars.

And on the cloud provider side, imagine how many 128 MB containers fit on a host.


shouldn't lan-local v6 interfaces suffice for that?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: