cfg dir #348

New issue

Closed

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

bsakaguchi commented

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

Owner

📋 Pull Request Information

Original PR: https://github.com/games-on-whales/wolf/pull/65
Author: @PierreBeucher
Created: 3/1/2024
Status: ✅ Merged
Merged: 3/2/2024
Merged by: @ABeltramo

Base: stable ← Head: minor-doc-update

📝 Commits (2)

849ff9e doc: populate volume using non-erroring command
36cb5ca fix: create cfg directory on container startup

📊 Changes

2 files changed (+11 additions, -6 deletions)

View changed files

📝 docker/startup.sh (+6 -0)
📝 docs/modules/user/pages/quickstart.adoc (+5 -6)

📄 Description

Hi there, I played a bit with Wolf and followed through the getting started documentation. Here's a few update suggestions for a better flow:

It's possible to create a Docker container to populate nvidia volume with docker create rather than use docker run which will exit with error - same result with a slightly better UX :)

Also Wolf expect a /etc/wolf/cfg directory to exists on startup and fails otherwise. This directory does not exists by default as only /etc/wolf is mounted. By mouting both /etc/wolf and /etc/wolf/cfg Docker will create both directories if they do not already exists, hence Wolf won't crash (as suggested here: https://github.com/games-on-whales/wolf/issues/64#issuecomment-1951479056)

_{🔄 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/wolf/pull/65 **Author:** [@PierreBeucher](https://github.com/PierreBeucher) **Created:** 3/1/2024 **Status:** ✅ Merged **Merged:** 3/2/2024 **Merged by:** [@ABeltramo](https://github.com/ABeltramo) **Base:** `stable` ← **Head:** `minor-doc-update` --- ### 📝 Commits (2) - [`849ff9e`](https://github.com/games-on-whales/wolf/commit/849ff9e3e19b744abf5ae303399caa53b00c69cc) doc: populate volume using non-erroring command - [`36cb5ca`](https://github.com/games-on-whales/wolf/commit/36cb5caeb55ee00c06630587bc0f62d9b348d06a) fix: create cfg directory on container startup ### 📊 Changes **2 files changed** (+11 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `docker/startup.sh` (+6 -0) 📝 `docs/modules/user/pages/quickstart.adoc` (+5 -6) </details> ### 📄 Description Hi there, I played a bit with Wolf and followed through the getting started documentation. Here's a few update suggestions for a better flow: It's possible to create a Docker container to populate nvidia volume with `docker create` rather than use `docker run` which will exit with error - same result with a slightly better UX :) Also Wolf expect a `/etc/wolf/cfg` directory to exists on startup and fails otherwise. This directory does not exists by default as only `/etc/wolf` is mounted. By mouting both `/etc/wolf` and `/etc/wolf/cfg` Docker will create both directories if they do not already exists, hence Wolf won't crash (as suggested here: https://github.com/games-on-whales/wolf/issues/64#issuecomment-1951479056) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

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