Feature Request: Allow configuration of Docker network pool (and consider changing the default)

[kachunkachunk]

To start, Docker is behaving correctly. But in HexOS, I'm seeing that the configured base 172.17.0.0/12 is technically invalid as a /12 network boundary, which is being normalized to 172.16.0.0/12.
This results in automatic allocation of 172.16.x.0/24 networks. If the intention is to allocate only from 172.17.x.x, the base should be changed to 172.17.0.0/16.

Practically speaking, when a user deploys apps, they typically appear to end up on new Docker bridge networks, which can quickly create IP conflicts for the few users out there using 172.16.x.x/16 networks.
I noticed this after the TrueNAS login page was showing up unexpectedly for one of my unrelated endpoints.

I'd suggest surfacing some configuration parameters somewhere in the UI, namely the Docker network pool config.

As a more immediate fix: To reconfigure my HexOS deployment to use the 172.17.0.0/16 network ranges instead, I ran:

root@HexOS[~]# midclt call docker.update '{
  "address_pools": [
    {
      "base": "172.17.0.0/16",
      "size": 24
    },
    {
      "base": "fdd0::/48",
      "size": 64
    }
  ]
}'

[mill3000]

Hello. Thanks for taking the time to write this. We did see the point of this and will roll it in to HexOS. Not sure when it will be releasaed but it will do this on new installs going forward once it's implimented. We don't want to cause any issues for anyone that's not currently affected.