Identical/Similar reports in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1712696
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592
Downstream, discussion on this in the Ubuntu Server Team indicated that
removing IPv6 support entirely on a system is what we consider an edge
case for setups, and probably not something we need to worry about on a
larger scale because most environments aren't set up without IPv6
support being completely disabled on the system (so you could still get
a local v6 bind, even if it's localhost).
We haven't made any movement on this because we considered it a very
edge-case setup and an issue with the end-user systems. This being
said, you can fix this *easily* by editing the default config then doing
`apt install -f` or `apt-get install -f` to fix the environment and
finish install/configuration. For autodeployed systems this might be
harder, but for the average case there's workarounds.
Thomas
