Do not change Docker's IP range

[TheDevMinerTV]

We have quite a bunch of VPNs that are in the 10.0.*.* range and installing Coolify entirely breaks those since it puts the Docker daemon into those subnets. Please allow us to disable that.

Changing the IP range in /etc/docker/daemon.json.coolify doesn't work either because Docker keeps using the old IP range since it's stored in /var/lib/docker/network/files/local-kv.db.

[andrasbacsai]

This is a great suggestion. I am thinking adding a possible override function, so like if you add a /etc/docker/daemon.json.override, with the following for example:

{
  "default-address-pools": [
    {"base":"192.168.0.0/8","size":24}
  ]
}

It will override the final daemon.json, so it will be like:

{
  "log-driver": "json-file",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  },
  "default-address-pools": [
    {"base":"192.168.0.0/8","size":24}
  ]
}

What do you think?

[Wheels35]

this is definitely something needed, as I am running into the IP address conflict as well, specifically for me on install.

Until this is solved, is there any harm in directly editing the install script, or would doing a manual install be better?

[vladflotsky]

@andrasbacsai any progress?

[andrasbacsai]

Now you can make a custom ip range during installation: https://coolify.io/docs/knowledge-base/define-custom-docker-network-with-env