Skip to content

Dockge on Unraid & startup order #911

@adrianmihalko

Description

@adrianmihalko

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

  • I checked and didn't find similar issue

🛡️ 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:

Image

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions