The future of Docker containers

Posted May 16, 2019 2:23 UTC (Thu) by foom (subscriber, #14868)
In reply to: The future of Docker containers by Cyberax
Parent article: The future of Docker containers

> NAT support needs to be added to IPv6

Blargh...I really hope not. That's so backwards...

It seems like a bug in aws if you cannot easily assign multiple ipv6 addresses to a host.

The future of Docker containers

Posted May 17, 2019 20:29 UTC (Fri) by flussence (guest, #85566) [Link] (3 responses)

>It seems like a bug in aws if you cannot easily assign multiple ipv6 addresses to a host.

It's price scalping, is what it is. OVH does the same thing with its cheaper dedi offerings, even though they already have the infra to allocate you a /56 on the rest.

The future of Docker containers

Posted May 17, 2019 20:47 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (2 responses)

?? You are not charged on a per-IP basis at Amazon. It's more like an architectural limitation, Amazon readily assigns a /56 prefix to your VPCs.

The future of Docker containers

Posted May 21, 2019 2:18 UTC (Tue) by foom (subscriber, #14868) [Link] (1 responses)

Looks like it's *possible* with aws, if not easy:
https://medium.freecodecamp.org/how-to-run-ipv6-enabled-d...

The future of Docker containers

Posted May 21, 2019 2:28 UTC (Tue) by Cyberax (✭ supporter ✭, #52523) [Link]

It basically manually assembles a network out of multiple individual IPv6 addresses. This is doable, but not at all nice. I'm not sure a simple IPv6 NAT is worse than that.

The better way is to just use a CNI plugin to dynamically create ENI (Amazon's virtual network interfaces) and assign them to containers directly.

You also still need a stateful firewall because you do NOT want to expose all containers' ports automatically.