starred/dockge-louislam

Fork 0

mirror of https://github.com/louislam/dockge.git synced 2026-03-03 02:06:55 -05:00

Dockge on Unraid & startup order #242

New issue

Open

opened 2026-02-20 13:12:30 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 13:12:30 -05:00

Owner

Originally created by @adrianmihalko on GitHub (Jan 5, 2026).

⚠️ Please verify that this bug has NOT been reported before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

I have a docker-compose file where it is important that the VPN starts first, and only then the other services.

This is how it looks now after I added it in Dockge:

Unfortunately, when I run a backup or restart the server, Unraid tries to start everything ASAP. I tried dragging the VPN container above the others, but that doesn’t help either, because it immediately starts the rest as well.

Although they do start, they are not accessible due to a network error.

My docker-compose file works perfectly in a real Docker Compose environment, because the VPN container starts first, and once it is up and running, the other services start.

services:
  vpn-pia:
    image: thrnz/docker-wireguard-pia
    container_name: vpn-pia
    cap_add:
      - NET_ADMIN
    volumes:
      - ./config/vpn-pia:/pia
      - ./config/vpn-pia:/pia-shared
      - ./pia-port.sh:/pia-port.sh
    ports:
      - 3003:3000 # StremHU UI
      - 3004:5000 # speedtest
    healthcheck:
      test:
        - CMD-SHELL
        - curl -fsS --max-time 5 https://api.ipify.org >/dev/null || exit 1
      interval: 15s
      timeout: 7s
      retries: 10
      start_period: 30s
    restart: unless-stopped
  stremhu-source:
    image: s4pp1/stremhu-source:dev
    container_name: stremhu-source
    depends_on:
      vpn-pia:
        condition: service_healthy
    network_mode: service:vpn-pia
    volumes:
      - ./data/database:/app/data/database
      - ./data/torrents:/app/data/torrents
      - ./data/downloads:/app/data/downloads
    restart: unless-stopped
  speedtest-app:
    image: adriankoooo/speedtest-app:latest
    container_name: speedtest-app
    depends_on:
      vpn-pia:
        condition: service_healthy
    network_mode: service:vpn-pia
    environment:
      - TZ=Europe/Budapest
    restart: unless-stopped
networks: {}

Once again, I’m not sure whether this is a bug or simply how Dockge works on Unraid.

👟 Reproduction steps

👀 Expected behavior

😓 Actual Behavior

Dockge Version

latest

💻 Operating System and Arch

Unraid

🌐 Browser

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

Originally created by @adrianmihalko on GitHub (Jan 5, 2026). ### ⚠️ Please verify that this bug has NOT been reported before. - [x] I checked and didn't find similar issue ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/dockge/security/policy) ### Description I have a docker-compose file where it is important that the VPN starts first, and only then the other services. This is how it looks now after I added it in Dockge: <img width="2872" height="1196" alt="Image" src="https://github.com/user-attachments/assets/48e083a2-350b-43e2-b9c0-7b1258107760" /> Unfortunately, when I run a backup or restart the server, Unraid tries to start everything ASAP. I tried dragging the VPN container above the others, but that doesn’t help either, because it immediately starts the rest as well. Although they do start, they are not accessible due to a network error. My docker-compose file works perfectly in a real Docker Compose environment, because the VPN container starts first, and once it is up and running, the other services start. ``` services: vpn-pia: image: thrnz/docker-wireguard-pia container_name: vpn-pia cap_add: - NET_ADMIN volumes: - ./config/vpn-pia:/pia - ./config/vpn-pia:/pia-shared - ./pia-port.sh:/pia-port.sh ports: - 3003:3000 # StremHU UI - 3004:5000 # speedtest healthcheck: test: - CMD-SHELL - curl -fsS --max-time 5 https://api.ipify.org >/dev/null || exit 1 interval: 15s timeout: 7s retries: 10 start_period: 30s restart: unless-stopped stremhu-source: image: s4pp1/stremhu-source:dev container_name: stremhu-source depends_on: vpn-pia: condition: service_healthy network_mode: service:vpn-pia volumes: - ./data/database:/app/data/database - ./data/torrents:/app/data/torrents - ./data/downloads:/app/data/downloads restart: unless-stopped speedtest-app: image: adriankoooo/speedtest-app:latest container_name: speedtest-app depends_on: vpn-pia: condition: service_healthy network_mode: service:vpn-pia environment: - TZ=Europe/Budapest restart: unless-stopped networks: {} ``` Once again, I’m not sure whether this is a bug or simply how Dockge works on Unraid. ### 👟 Reproduction steps - ### 👀 Expected behavior - ### 😓 Actual Behavior - ### Dockge Version latest ### 💻 Operating System and Arch Unraid ### 🌐 Browser - ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output ```shell ```

deekerman added the

bug

label

2026-02-20 13:12:30 -05:00

deekerman commented

2026-02-20 13:12:32 -05:00

Author

Owner

@starfishpatkhoo commented on GitHub (Feb 16, 2026):

Just wanted to add, this is not a bug within dockge. Docker compose cannot set a depends_on across multiple docker-compose stacks, only for services within the same docker-compose stack. Doesn't matter if you were running Unraid or not.

I use Unraid also, and the way I go about this is by using depends_on but defining each individual service as an include from within one single docker-compose stack. Because it is part of one single / same stack, you can now use depends_on and make sure the core service (like your VPN) is started before starting the other services. Then, this one stack is what you set Unraid to auto-start.

Unfortunately, dockge does not handle include files well (see https://github.com/hamphh/dockge/issues/9) .. You may need to rewrite/tweak your compose yml files to be properly included, but this solution works. It separates the individual services into their own folders/spaces, it allows for dependencies, and it works with Unraid's auto-start in a predictable and define-able manner.

@starfishpatkhoo commented on GitHub (Feb 16, 2026): Just wanted to add, this is not a bug within dockge. Docker compose cannot set a `depends_on` across multiple docker-compose stacks, only for services within the same docker-compose stack. Doesn't matter if you were running Unraid or not. I use Unraid also, and the way I go about this is by using `depends_on` but defining each individual service as an `include` from within one single docker-compose stack. Because it is part of one single / same stack, you can now use `depends_on` and make sure the core service (like your VPN) is started before starting the other services. Then, this one stack is what you set Unraid to auto-start. Unfortunately, dockge does not handle `include` files well (see https://github.com/hamphh/dockge/issues/9) .. You may need to rewrite/tweak your compose yml files to be properly `include`d, but this solution works. It separates the individual services into their own folders/spaces, it allows for dependencies, and it works with Unraid's auto-start in a predictable and define-able manner.

deekerman commented

2026-02-20 13:12:32 -05:00

Author

Owner

@starfishpatkhoo commented on GitHub (Feb 16, 2026):

Sorry, it just occurs to me that you might be using Unraid Docker? You need to use Unraid Docker Compose, and then, make sure you only set auto-start for the one stack (that rules them all), not individual services. Not sure if that's more what you're facing (can't recall the Unraid screen ...

EDIT:

Your compose yml should have some extras to indicate management via Unraid Docker Compose...

    labels:
      # ---- Some Unraid specific UI stuff
      net.unraid.docker.managed: composeman       # If this is managed via dockerun, it would be "dockerman"
      # Look for application Icons here (PNGs are best for Unraid, no SVGs): https://dashboardicons.com/icons
      net.unraid.docker.icon: _icon_url_
      net.unraid.docker.webui: http://[IP]:[PORT:_host_port_]/
      net.unraid.docker.shell: null

or something like that.. ^_^

@starfishpatkhoo commented on GitHub (Feb 16, 2026): Sorry, it just occurs to me that you might be using Unraid Docker? You need to use Unraid Docker Compose, and then, make sure you only set auto-start for the one stack (that rules them all), not individual services. Not sure if that's more what you're facing (can't recall the Unraid screen ... EDIT: Your compose yml should have some extras to indicate management via Unraid Docker Compose... ``` labels: # ---- Some Unraid specific UI stuff net.unraid.docker.managed: composeman # If this is managed via dockerun, it would be "dockerman" # Look for application Icons here (PNGs are best for Unraid, no SVGs): https://dashboardicons.com/icons net.unraid.docker.icon: _icon_url_ net.unraid.docker.webui: http://[IP]:[PORT:_host_port_]/ net.unraid.docker.shell: null ``` or something like that.. ^_^