Container process listening on ipv6-only port unreachable from published container dual-stack port

If a container process is listening on an IPv6 only port, like [::]:8080, and that port is published as 8000 on the host, it will not be reachable via the host port. The host port will be a dual-stack binding (*:8000) and that seems to be unable to forward the connection through to a v6 single-stack binding.

Changing the container's binding to a dual-stack binding will resolve this issue. This showed up in an NGINX container.

I am not really sure where this issue belongs or what to do about it, it's really a documentation item. Adding to this project to it does not get lost.