Upon restart some stacks never start

[liquidfrollo]

⚠️ 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

When the host is restarted (Truenas scale running jlmkr / dockge) some stacks start but others show exited or not up completely. If i go into the stacks manually and click start they start without issue.

👟 Reproduction steps

Restart the host

👀 Expected behavior

all stacks should start without issue

😓 Actual Behavior

some stacks do not start. Speculation that the docker sock exposed by traefik is not available and is required by other stacks, no way to do "depends on" between stacks.

Dockge Version

1.4.2

💻 Operating System and Arch

Truenas Scale (24.0.4.2.3) / Jlmkr running - Debian release 12 codename bookworm

🌐 Browser

Firefox - most current

🐋 Docker Version

20.10.24+dfsg1

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[wsw70]

the docker sock exposed by traefik is not available

I am not sure I understand: the docker socket is provided by docker (and the OS) and Traefik just makes use of it.

[louislam]

Might be the wrong status bug, which I still don't know how to 100% reproduce it. They maybe actually up.

[liquidfrollo]

The apps themselves are NOT up. Take the arr's stack above where some say started and some are not. The overseerr app is up however sonarr / radarr is not and returns a 404 when i attempt to access. I wish i could stack rank or priority order start the compose files at a minimum (assuming i couldn't depend on another app in a diff stack) to buy time for the picky stacks such as my arr's stack.

With respect to the docker sock. from a security perspective, the docker sock is not directly exposed and instead is exposed through the socket-proxy service seen in the traefik stack. I tried making other stacks depend on the status of another however that doesn't work because you can't make one compose depend on another (from what i gathered)

[markwaters]

I'm having the same issue , but I am new to docker so it may be that.
I have linkding , readeck and uptime-kuma setup and working.
However readeck doesn't start , or perhaps does start and fails.
If I start it manually it works perfectly.

[liquidfrollo]

same for me in that if i restart it manually it works. It just never fully loads on a server restart.

[markwaters]

I created a new ProxMox LXC , installed Docker - just the command line version this time.
Copied the data directory across.
This starts Readeck on Host restart every time so far.

[liquidfrollo]

Glad your issue is resolved however, mine is not and i have no indication why those containers won't start without manual intervention

[InnocentRain]

I pretty much have the same issue, some containers don't start after a reboot, but only about 20% of the time.

[N0rga]

I'm having the same issue as @liquidfrollo. Any containers within Dockge don't automatically start when my server is rebooted. They're all in individual stacks as well, with ARR apps pointing back to Gluetun for VPN/Network. (Understand that this is probably not the ideal configuration)