Start by enabling IPv6 on your docker daemon: https://docs.docker.com/config/daemon/ipv6/ https://docs.docker.com/config/daemon/ipv6/ I assume your scenario is

Start by enabling IPv6 on your docker daemon: https://docs.docker.com/config/daemon/ipv6/ https://docs.docker.com/config/daemon/ipv6/ I assume your scenario is that you don't currently use IPv6, so you probably can't assign a subnet of your /48 block of IPv6 range to be routed to your docker host. You can probably use a subnet from a reserved range in that case, for example from: https://en.wikipedia.org/wiki/Unique_local_address https://en.wikipedia.org/wiki/Unique_local_address With that new subnet set up, you would at least be able to test the services running inside containers from that host itself. In my own experience I never encountered services that don't work with IPv6 at all, but as others mentioned the most common issues are with truncated addresses in a db column designed for IPv4 or log parsers that refuse to match on IPv6. Worst case I found was a log based rate limiter that ignored IPv6 addresses and therefore let all requests using that stack pass.