[PR #46] [MERGED] Set HOST_APPS_STATE_FOLDER so Wolf app containers use appdata not /etc #62

New issue

Closed

opened 2026-10-15 12:55:17 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 12:55:17 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/games-on-whales/unraid-plugin/pull/46
Author: @JBailes
Created: 5/30/2026
Status: ✅ Merged
Merged: 5/30/2026
Merged by: @JBailes

Base: main ← Head: aimee/session/d6325657

📝 Commits (3)

5d5ecfe Replace split auto-tag + release workflows with a single auto-release workflow
92ae464 Set HOST_APPS_STATE_FOLDER so Wolf app containers use appdata not /etc
558cfb2 Merge remote-tracking branch 'origin/main' into aimee/session/d6325657

📊 Changes

2 files changed (+3 additions, -0 deletions)

View changed files

📝 gow.plg (+1 -0)
📝 scripts/deploy.sh (+2 -0)

📄 Description

Problem

When Wolf spawns additional Docker containers, it bind-mounts their app state from ${HOST_APPS_STATE_FOLDER}/profile_data/... on the host. That variable defaults to /etc/wolf. The previous fix mounted the configured appdata directory at /etc/wolf inside the Wolf container, which fixed Wolf's own config — but left HOST_APPS_STATE_FOLDER unset, so child containers still landed in host /etc/wolf instead of the chosen appdata path.

Fix

Set HOST_APPS_STATE_FOLDER=${APPDATA} in the Wolf container environment for both the NVIDIA and standard compose definitions, so Wolf tells the host Docker daemon to bind-mount spawned app state from the configured appdata directory.

Notes

Requires redeploy (re-save settings / re-run deploy) to regenerate docker-compose.yml, then restart the stack.
Existing app state already written to host /etc/wolf is not moved automatically.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/games-on-whales/unraid-plugin/pull/46 **Author:** [@JBailes](https://github.com/JBailes) **Created:** 5/30/2026 **Status:** ✅ Merged **Merged:** 5/30/2026 **Merged by:** [@JBailes](https://github.com/JBailes) **Base:** `main` ← **Head:** `aimee/session/d6325657` --- ### 📝 Commits (3) - [`5d5ecfe`](https://github.com/games-on-whales/unraid-plugin/commit/5d5ecfe379a7ba338769873450517b43ab92bf7a) Replace split auto-tag + release workflows with a single auto-release workflow - [`92ae464`](https://github.com/games-on-whales/unraid-plugin/commit/92ae46465230b950ed6168c97b7280992f45d6f6) Set HOST_APPS_STATE_FOLDER so Wolf app containers use appdata not /etc - [`558cfb2`](https://github.com/games-on-whales/unraid-plugin/commit/558cfb2a347790c8e6efe5bbba58e96321fda246) Merge remote-tracking branch 'origin/main' into aimee/session/d6325657 ### 📊 Changes **2 files changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `gow.plg` (+1 -0) 📝 `scripts/deploy.sh` (+2 -0) </details> ### 📄 Description ## Problem When Wolf spawns additional Docker containers, it bind-mounts their app state from `${HOST_APPS_STATE_FOLDER}/profile_data/...` on the host. That variable defaults to `/etc/wolf`. The previous fix mounted the configured appdata directory at `/etc/wolf` *inside* the Wolf container, which fixed Wolf's own config — but left `HOST_APPS_STATE_FOLDER` unset, so child containers still landed in host `/etc/wolf` instead of the chosen appdata path. ## Fix Set `HOST_APPS_STATE_FOLDER=${APPDATA}` in the Wolf container environment for both the NVIDIA and standard compose definitions, so Wolf tells the host Docker daemon to bind-mount spawned app state from the configured appdata directory. ## Notes - Requires redeploy (re-save settings / re-run deploy) to regenerate `docker-compose.yml`, then restart the stack. - Existing app state already written to host `/etc/wolf` is not moved automatically. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-15 12:55:17 +00:00