Used docker network in coolify server instance is 10.0.0.0 - collision

[pongraczi]

Hi,

First of all, thanks for this cool project, it is just amazing!

Regarding to the subject, short version:
It would be nice to be able to change the docker used network from 10.0.0.0/24 to something else from the UI or install time.

Longer version:
In my hybrid cloud network (Hetzner VPS + dedicated servers with Proxmox), the network 10.0.0.0/16 is already used.
When I installed a coolify instance into a Hetzner VPS, docker just acquires the 10.0.0.0/24 and 10.0.2.0/24 networks, which blocks reaching other services in the 10.0.0.0/16 network I already have.
The reason of this is that, we should access directly other servers/services which are on the internal network.

As I checked the situation, the installation script has a hardcoded value and it will overwrite my modifications, which is a little bit rude, but obviously effective.

Here is the relevant part of the install script:

...
echo -e "4. Check Docker Configuration. "
mkdir -p /etc/docker
# shellcheck disable=SC2015
test -s /etc/docker/daemon.json && cp /etc/docker/daemon.json /etc/docker/daemon.json.original-"$DATE" || cat >/etc/docker/daemon.json <<EOL
{
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  },
  "default-address-pools": [
    {"base":"10.0.0.0/8","size":24}
  ]
}
EOL
cat >/etc/docker/daemon.json.coolify <<EOL
{
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  },
  "default-address-pools": [
    {"base":"10.0.0.0/8","size":24}
  ]
}
EOL
...

So, what I would like to see here is {"base":"10.137.0.0/8","size":24} or something else, for example, if the network settings differs from the 10.0.0.0, the installation should keep this value, instead of just overwriting it without a warning (sure, I did not expect the daemon.json will be overwritten :) )

Notes
I tried to reconfigure the network and according to the forums, (after removing messed containers) running the installation script again can restore (upgrade) them, which is pretty cool. It just did, reconfigured its network, but it overwrote the daemon and I am still on a dead subnet :)

I

[pongraczi]

Hetzner Coolify app

• Network collision as described above.
  (Please note that, I used Hetzner's coolify app image, where I experienced this kind of collision.) 🙅

Hetzner docker app + manual coolify install

• I got an other network pool, no need to create daemon.json -> everything just works. ✔️
• I only just followed the documentation and I got a working coolify server.
• Please note, this coolify server will not host anything else.

[djsisson]

@pongraczi i've no idea why they changed the default-address-pool, i know they needed to change the size, due to being limited to 32 networks.

But imo it should have been left as default 172.17.0.0, and instead change to the following:

{
  "default-address-pools" : [
    {
      "base" : "172.17.0.0/12",
      "size" : 20
    },
    {
      "base" : "192.168.0.0/16",
      "size" : 24
    }
  ]
}

The other reason is 10.0.x.x is also used for docker swarm mode, as well as default in a lot of private networks like you mention