Use distinguishable (human-readable) bridge interface name instead of br-7da...

[Talkless]

Hi,

Currently in my installation (Debian 12 host) Docker has created bridge interface with name br-7da043d4db4d.

Zone-based firewall managers like firewalld, Shorewall, foomuuri, etc., needs to specify interface names to map it into the zone, and having br-7da043d4db4d specified there is kinda not really self-explanatory, nor "stable". I guess reinstalling Coolify or doing other changes might change that generated name?

Apparently, docker supports setting custom interface name, so docker-componse.yaml could looke something like this (NOT actually tested):

networks:
    coolify:
        name: coolify
        driver: bridge
        external: false
        networks:
        driver_opts:
            com.docker.network.bridge.name: br-coolify

See: https://docs.docker.com/engine/network/drivers/bridge/#options
See: https://docs.docker.com/reference/compose-file/networks/#driver_opts

[djsisson]

i think this is one of those things which is so niche, to specific users it probably won't get altered, however there is an option to set this

create this file
/data/coolify/source/docker-compose.custom.yml
contents:

networks:
    coolify:
        driver_opts:
            com.docker.network.bridge.name: br-coolify

this would get merged with the compose when installing/upgrading, meaning you are free to choose what you want here

[Talkless]

Cool, didn't new there was custom.yml!

But it has no effect after install.sh ("upgrade"), maybe it would have effect only during first install..?

root@vcoolify:/data/coolify/source# head -n1 upgrade-2025-05-27-14-59-27.log 
docker-compose.custom.yml detected.

root@vcoolify:/data/coolify/source# cat docker-compose.custom.yml 
networks:
  coolify:
    driver_opts:
      com.docker.network.bridge.name: br-coolify

root@vcoolify:/data/coolify/source# ip link | fgrep -e ": br-coolify" -e ": br-"
4: br-7da043d4db4d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default

[djsisson]

ah, yes it only takes effect on intial creation, so it would need to be removed first

infact, the network is pre created before the compose, so in this instance it would not do anything

coolify/scripts/upgrade.sh

Line 35 in fc5138f

if ! docker network create --attachable --ipv6 coolify 2>/dev/null; then

so you would need to create the network first, however since the interface name is not a cli option, this can't be done in the script, it can only be pre created in a compose first

so before running coolify, you would jsut need to run any compose creating the coolify network, with an interface name, from then on it's fine, since the network is never deleted

[Talkless]

so before running coolify, you would jsut need to run any compose

That's too nitty-gritty. Would be nice to have some sort of DOCKER_BRIDGE_NAME env for instal.sh...

[djsisson]

Well the script would need changing since you can't give it a name using docker network create

Running ip addr show to get the interface seems a lot easier than changing the behaviour of the coolify network from external.

[Talkless]

Well the script would need changing

Yes, that's the point of feature requests :) .

I doubt it would hurt to have --opt com.docker.network.bridge.name=br-coolify argument in that docker network create line.

Unless multiple Coolify instances are being supported on the same host, which is not and will be not?

[djsisson]

Ah sorry yes I was getting mixed up it's only the docker interface you can't name in the cli,

You can just make a pr if you think it needs changing, it's not something anyone else has mentioned needing changing, but your suggestion makes sense for those that need this feature.