BUG] IPv6 network is always treated as /64, even when specified otherwise · Issue #10807 · docker/compose · GitHub
![External Pi-hole with IPv6 – Setup a secured Pi-hole DNS service on Docker using Linode/AWS - multicastbits.com External Pi-hole with IPv6 – Setup a secured Pi-hole DNS service on Docker using Linode/AWS - multicastbits.com](https://www.multicastbits.com/wp-content/uploads/2020/07/Piholecloud1.png)
External Pi-hole with IPv6 – Setup a secured Pi-hole DNS service on Docker using Linode/AWS - multicastbits.com
![networking - Accessing docker-compose containers via ipv6 from the outside of the docker host - Server Fault networking - Accessing docker-compose containers via ipv6 from the outside of the docker host - Server Fault](https://i.stack.imgur.com/9H7xW.png)
networking - Accessing docker-compose containers via ipv6 from the outside of the docker host - Server Fault
![Help: Understanding Docker Networking, IPVlan/Macvlan and IPv6 behaviour - General - Docker Community Forums Help: Understanding Docker Networking, IPVlan/Macvlan and IPv6 behaviour - General - Docker Community Forums](https://global.discourse-cdn.com/docker/original/3X/9/4/943cdb82aa3647e6209a1bb7b9549b4039d35556.png)
Help: Understanding Docker Networking, IPVlan/Macvlan and IPv6 behaviour - General - Docker Community Forums
![Both IPv4 and IPv6 address are assigned automatically even it has been specified in docker compose file · Issue #14737 · containers/podman · GitHub Both IPv4 and IPv6 address are assigned automatically even it has been specified in docker compose file · Issue #14737 · containers/podman · GitHub](https://user-images.githubusercontent.com/100113781/175947296-bc42f536-b24b-4598-88ba-fa7c87cea623.png)