fuse") crashes Wolf instead of showing a config error #320

New issue

Open

opened 2026-10-15 12:59:37 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 12:59:37 +00:00

Owner

Originally created by @To0wnn on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/527

What happens
If a runner's devices entry is just a path, e.g. devices = ["/dev/fuse"], Wolf aborts while reading the config and keeps restarting. The log only shows a stack trace (abort in the config parser), so it took a while to find the cause.

Expected
Either accept a bare path (use the same path inside the container, like Docker does), or log a clear error like invalid device definition "/dev/fuse", expected host:container[:permissions] instead of crashing.

The format isn't mentioned in the configuration docs either; a one-line example would help.

Setup
ghcr.io/games-on-whales/wolf:stable (built 2026-09-29), rootful podman.

Originally created by @To0wnn on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/527 **What happens** If a runner's `devices` entry is just a path, e.g. `devices = ["/dev/fuse"]`, Wolf aborts while reading the config and keeps restarting. The log only shows a stack trace (abort in the config parser), so it took a while to find the cause. **Expected** Either accept a bare path (use the same path inside the container, like Docker does), or log a clear error like `invalid device definition "/dev/fuse", expected host:container[:permissions]` instead of crashing. The format isn't mentioned in the configuration docs either; a one-line example would help. **Setup** `ghcr.io/games-on-whales/wolf:stable` (built 2026-09-29), rootful podman.