ADVERTISE_ADDR on installation is not working

[ecoskun87]

To Reproduce

When installing Dokploy with Docker already present, the install script automatically leaves any existing swarm and re-initializes it.
Even when the environment variable ADVERTISE_ADDR is set, the script ignores it and always uses the Docker bridge IP (172.17.0.1) as the swarm advertise address.

1. Ensure Docker is installed and running.
2. Set the desired advertise address:
   export ADVERTISE_ADDR=10.50.50.1
3. Run the Dokploy install script:
   curl -sSL https://dokploy.com/install.sh | sudo sh
4. Observe the output:
   Node left the swarm.
   Using advertise address: 172.17.0.1
   Swarm initialized: current node (...) is now a manager.

Current vs. Expected behavior

Expected behavior
The script should respect the ADVERTISE_ADDR environment variable and initialize the swarm using the specified IP (10.50.50.1 in this case).

Actual behavior
The script ignores ADVERTISE_ADDR and chooses 172.17.0.1 (Docker bridge IP) instead.

Workarounds

• Manually initialize the swarm with docker swarm init --advertise-addr 10.50.50.1 before running the script.
• Modify the script to hardcode the desired advertise address.

Environment

• Dokploy version: v0.28.6
• Docker version: (any recent stable version)
• OS: Debian-based Linux
• Use case: Installing Dokploy behind WireGuard private network

Provide environment information

S: Debian GNU/Linux 13 (trixie)
Kernel: 6.1.0-10-amd64
Architecture: x86_64
Docker: 28.5.0

Which area(s) are affected? (Select all that apply)

Installation

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

[dosubot]

Hi @ecoskun87! I'm Dosu and I’m helping the dokploy team.

The issue is that when you run curl ... | sudo sh, environment variables exported in your user shell don't pass through sudo to the script. So even though you exported ADVERTISE_ADDR=10.50.50.1, the root shell executing the script never received it and fell back to automatic IP detection.

Solution - Pass the variable inline to sudo:

curl -sSL https://dokploy.com/install.sh | sudo ADVERTISE_ADDR=10.50.50.1 sh

Or use sudo -E to preserve your environment:

export ADVERTISE_ADDR=10.50.50.1
curl -sSL https://dokploy.com/install.sh | sudo -E sh

If you already installed with the wrong IP, you can fix it by re-initializing the swarm:

docker swarm init --force-new-cluster --advertise-addr 10.50.50.1

The install script does support ADVERTISE_ADDR, but its fallback get_private_ip() function takes the first RFC1918 private IP it finds, which often matches Docker bridge interfaces (172.17.x.x) before actual host interfaces.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}