We know this as IPv6, which increases the IP address size from 32 bits to 128 bits. This process is know as Network Address Translation ( NAT) and was defined a couple of months later.Ībout a year later (1995), a new version of the Internet Protocol came out to provide - among other things - expanded addressing capabilities. If any of these hosts need to connect to an outside host, its address needs to be translated into a - public - IP address that is globally unique. You use these to identify hosts private to an enterprise. This is actually the fourth version of the protocol, so we refer to these addresses as IP version 4 ( IPv4) addresses.Īpproximately a decade later, in 1992, it became evident that we would eventually run out of 32-bit IPv4 addresses, so in march 1994, re-usable private IP addresses were defined in an attempt to preserve IP address space. When the Internet protocol ( IP) that helps deliver this blog post to your device was defined back in 1981, the internet addresses that identify sources and destinations were specified as fixed length of four octets ( 32 bits). On the other hand, there is no shortage of IPv6 addresses, so you could in theory assign a unique one to as many containers as you’d like. Unfortunately, the price of each IPv4 address is exceeding $20, so you won’t get one for each and every one of your containers. How to run IPv6-enabled Docker containers on AWSĭo you want to forget about NAT and run containers without having to translate IP addresses? Then you need public IP addresses, lots of them.

Docker mac address web traffic blocked