mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 13:02:03 +00:00
[GH-ISSUE #270] wolf fails to start at system restart ( restart: unless-stopped ) #188
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#188
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ironoa on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/270
TL;DR Just annoying, the quick fix is to manually "restart" wolf (
docker restart wolf) or the docker deamon when the system starts up. The issue is present when using theNvidia Manualdeployment approach.wolf is configured to spawn at system startup (
restart: unless-stopped), but it fails to do so with the following error:If one manually restarts the docker deamon or the wolf container, it then works. I also tried to delay the startup of the docker deamon at startup, but with no luck.
After the manual restart, the logs are the following:
On a side node, probably not directly related, I noticed this warning:
To replicate it, one just need to run
docker compose up -dfor the following compose filefrom the official guide (Nvidia Manual), and then restart the container. From there on, the only way to make the warning disappear is to manually
docker kill wolf && docker rm wolf. The next run it won't have the warning, but all the subsequent ones will have the warning again.@ironoa commented on GitHub (Oct 23, 2025):
The issue is fixed/not present if one uses the documented
Nvidia (Container Toolkit)approach rather than theNvidia (Manual). Hopefully it will become the recommended stable approach: https://github.com/games-on-whales/wolf/issues/152FYI https://github.com/games-on-whales/wolf/pull/279