[PR #45] [MERGED] Fix Wolf Den port not applying from the GUI #61

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/45
Author: @JBailes
Created: 5/30/2026
Status: ✅ Merged
Merged: 5/30/2026
Merged by: @JBailes

Base: main ← Head: fix/wolf-den-port-publish

📝 Commits (2)

5d5ecfe Replace split auto-tag + release workflows with a single auto-release workflow
f1cf853 Fix Wolf Den port not applying by publishing host port to container 8080

📊 Changes

5 files changed (+108 additions, -102 deletions)

View changed files

➕ .github/workflows/auto-release.yml (+100 -0)
➖ .github/workflows/auto-tag.yml (+0 -40)
➖ .github/workflows/release.yml (+0 -56)
📝 gow.plg (+4 -1)
📝 scripts/deploy.sh (+4 -5)

📄 Description

Problem

Setting a custom Wolf Den port in the Unraid GUI had no effect — Wolf Den stayed on 8080.

In 541cab4 Wolf Den was switched from publishing its port to network_mode: host plus ASPNETCORE_URLS=http://0.0.0.0:${WOLF_DEN_PORT}. With host networking, Docker port publishing is ignored and the container binds host ports directly, so the only lever is the app's own bind address — and that ASPNETCORE_URLS override never took effect on the wolf-den image, leaving it on its default 8080.

Fix

Revert the wolf-den service (in both write_compose_nvidia and write_compose_standard) to bridge networking with a published port:

    ports:
      - "${WOLF_DEN_PORT}:8080"

The container keeps listening on its well-supported default 8080 internally, and Docker maps the GUI-specified host port onto it. Wolf Den only talks to Wolf over the shared wolf-socket unix-domain socket (not the network), so it does not need host networking. Also removed the now-unused WOLF_DEN_LISTEN_URL variable.

Notes

Deploy-time change: existing installs must re-run Install/Reconfigure (or Update) to regenerate docker-compose.yml.
Verified bash -n scripts/deploy.sh passes; no stray ASPNETCORE_URLS / WOLF_DEN_LISTEN_URL / host-networking references remain on the wolf-den service.

_{🔄 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/45 **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:** `fix/wolf-den-port-publish` --- ### 📝 Commits (2) - [`5d5ecfe`](https://github.com/games-on-whales/unraid-plugin/commit/5d5ecfe379a7ba338769873450517b43ab92bf7a) Replace split auto-tag + release workflows with a single auto-release workflow - [`f1cf853`](https://github.com/games-on-whales/unraid-plugin/commit/f1cf853a075b252570b0533f6c5eaf46582c3ba9) Fix Wolf Den port not applying by publishing host port to container 8080 ### 📊 Changes **5 files changed** (+108 additions, -102 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/auto-release.yml` (+100 -0) ➖ `.github/workflows/auto-tag.yml` (+0 -40) ➖ `.github/workflows/release.yml` (+0 -56) 📝 `gow.plg` (+4 -1) 📝 `scripts/deploy.sh` (+4 -5) </details> ### 📄 Description ## Problem Setting a custom Wolf Den port in the Unraid GUI had no effect — Wolf Den stayed on `8080`. In `541cab4` Wolf Den was switched from publishing its port to `network_mode: host` plus `ASPNETCORE_URLS=http://0.0.0.0:${WOLF_DEN_PORT}`. With host networking, Docker port publishing is ignored and the container binds host ports directly, so the only lever is the app's own bind address — and that `ASPNETCORE_URLS` override never took effect on the `wolf-den` image, leaving it on its default `8080`. ## Fix Revert the `wolf-den` service (in both `write_compose_nvidia` and `write_compose_standard`) to bridge networking with a published port: ```yaml ports: - "${WOLF_DEN_PORT}:8080" ``` The container keeps listening on its well-supported default `8080` internally, and Docker maps the GUI-specified host port onto it. Wolf Den only talks to Wolf over the shared `wolf-socket` unix-domain socket (not the network), so it does not need host networking. Also removed the now-unused `WOLF_DEN_LISTEN_URL` variable. ## Notes - Deploy-time change: existing installs must re-run Install/Reconfigure (or Update) to regenerate `docker-compose.yml`. - Verified `bash -n scripts/deploy.sh` passes; no stray `ASPNETCORE_URLS` / `WOLF_DEN_LISTEN_URL` / host-networking references remain on the wolf-den service. --- <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

closed this issue
added the
pull-request
label

No labels

enhancement

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

games-on-whales/unraid-plugin#61

No description provided.

Rows
Columns