mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #291] [LXC] Error during container init: open sysctl net.ipv4.ip_unprivileged_port_start file: reopen fd 8: permission denied #202
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#202
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 @Gailoks on GitHub (Nov 16, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/291
After a long break, I decided to come back to Wolf.
A lot has changed since the last time I used it, so I was ready to jump into a new adventure.
But unexpectedly, nothing worked the way I hoped. Now I need help to get everything running again.
I’m running Wolf inside an LXC container following the official instructions. Game libraries and user home directories are stored on mergerfs.
The host system is Proxmox VE 8.4.14 with kernel 6.8.12-16-pve. I’m not yet ready to migrate to PVE 9, so I’m staying on this branch for now.
Here is my docker-composy.yml
And here goes logs
@ABeltramo commented on GitHub (Nov 16, 2025):
You have a bunch of legacy and wrong variables and mount points; let's reset a bit and start back with the recomended options 😉
Does the following works for you?
And please reset the
config.tomlto the default file. Once you've got something that works we can start adding custom options if needed.@Gailoks commented on GitHub (Nov 16, 2025):
I used minimal amount of configuration options as you recommended
and got no success, also, config is default.
docker-compose.yml:
Logs:
@ABeltramo commented on GitHub (Nov 16, 2025):
The main issue seems to be:
Which seems to be an issue with mounting the
XDG_RUNTIME_DIR, can you post the full logs from the beginning instead of just parts of it? There's probably a warning up before what you posted here.You have also a whole bunch of other issues related to your iGPU. It seems that your Intel iGPU might be too old for our stack, which CPU do you have? You could try using the second GPU with something like:
but that might need some further adjustment (NEEDS TESTING)
@ABeltramo commented on GitHub (Nov 16, 2025):
Also, it might be worth to share your LXC
.conffile since there might be something wrong there too..@Gailoks commented on GitHub (Nov 16, 2025):
Here is my hardware:
Xeon e5 2680v4
64Gb ecc ddr4
gpu1: Intel arc a380 (It worked fine previously)
gpu2: AMD Rx 6800
LXC config
Full logs with your latest changes:
@Gailoks commented on GitHub (Nov 16, 2025):
I tried migrating to Docker 26.0.2, but that didn’t help either — neither the Wolf UI nor the stable builds work any better.
@ABeltramo commented on GitHub (Nov 16, 2025):
Your issue is
which seems to be completely unrelated to Wolf. After a quick search I've found this issue which might be helpful you should try and see if changing the apparmor rules like they do fixes it for you too..
@Gailoks commented on GitHub (Nov 17, 2025):
Thanks! The issue is gone — everything is working as it should now.
For reference, here is my full LXC config. I think the official guide should probably be updated to reflect newer Proxmox security requirements: