As far as I'm getting from all the available documentation on docker with IPv6, it doesn't seem to be designed in a way to be usable in practice.

1.) enabling it requires specific docker daemon startup options, but does anybody even start the docker daemon manually on a production machine? Usually, the init system handles this and when I start to use things it's already running. Am I supposed to restart the whole docker daemon just to enable IPv6? Apparently, there is no /etc/docker.conf or something similar either which would be an obvious point to enable it forever.

2.) as far as I've read the IPs are randomly assigned, but there is no NAT functionality available and these are actually public IPs. (side note: to my knowledge, NAT is still possible with IPv6 albeit unusual - so this could be possible to implement at least as an option, in the future) Apparently, I can't explicitly specify a static IPv6 for a container either even if I wanted to. This all means that I see no easy way to tell how a docker container will be reachable from the outside, and I can't reliably assign a public domain to it. How can I run a public server like that?

Since we're in 2015 now and last reserves of new IPv4 addresses will run out in a few months and people are actually already causing routing conflicts over spare IPv4 addresses (see recent news articles), it would be nice if IPv6 could be fixed to be more usable for practical use.