mirror of
https://github.com/games-on-whales/LXC2Docker.git
synced 2026-10-16 05:12:04 +00:00
[GH-ISSUE #53] Wolf breaks Proxmox shell/ssh #1
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/LXC2Docker#1
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 @paulzzh on GitHub (Jun 4, 2026).
Original GitHub issue: https://github.com/games-on-whales/LXC2Docker/issues/53
Proxmox VE 9.2.3 (kernel 7.0.6-2-pve)
Create a container:
Unable to open the web console:
SSH failed with
Server refused to allocate pty.This issue was caused by wolf breaking
/dev/ptsand/dev/ptmx, which prevented PTY allocation.This may be an upstream issue in wolf. Mounting the entire
/devinto the container may be too risky, since it can interfere with device nodes such as/dev/ptsand/dev/ptmx. After removing the/devmount, the main wolf container still starts, but I could not fully verify because the child containerwolfpulseaudiois currently blocked by another mount issue.generated
1001.confwolfpulseaudiogenerated
1000.confwolf@JBailes commented on GitHub (Jun 4, 2026):
Thank you for the report. I installed a new copy of Proxmox and managed to duplicate this.
I'm working on a fix.
@JBailes commented on GitHub (Jun 4, 2026):
Okay. The fix was pretty simple, I pushed a fix for the major issue. I'm still looking into the pulse audio issues, but I've merged a fix for the other issues @paulzzh
@JBailes commented on GitHub (Jun 4, 2026):
Ugh, this shouldn't have been closed. Gotta fix some scripts.
@paulzzh I also pushed an update for pulseaudio, but that one was a lot more complicated. Let me know if this fixes the issues.
@paulzzh commented on GitHub (Jun 5, 2026):
Failed to create
wolfpulseaudiocontainer. Fixed by adding--storage-opt size=8GBut it still cannot be started.
generated
1001.confwolfpulseaudio@JBailes commented on GitHub (Jun 5, 2026):
Thanks @paulzzh, that was exactly the info needed. Both remaining failures are now fixed in #59 (merged to main).
1. The
wolfpulseaudiomount failure (EINVAL). Wolf passes its ownXDG_RUNTIME_DIR(/run/user/wolf) to the PulseAudio sibling so they can share the audio socket, but Wolf creates that directory at runtime inside its own mount namespace, so nothing on the host backs it. The previous fix could only resolve it through Wolf's live namespace as/proc/<pid>/root/run/user/wolf, and the kernel refuses to bind-mount a path that lives in another container's namespace, which is theInvalid argumentyou saw. (That is also why the error changed from the earlierNo such file or directory: the path now resolves, but the mount itself is rejected.)The fix host-backs
XDG_RUNTIME_DIR: the daemon creates a real host directory and binds it into Wolf at/run/user/wolf, so when the PulseAudio container is created sharing that path it resolves to the same stable host directory. Both containers then bind an ordinary host path, like sharing through a Docker volume, and it survives Wolf restarting.2. The
refusing create ... below 2.0GiB threshold. The disk-pressure guardrail was inspecting that shared runtime dir, which is a small tmpfs, and a tmpfs reporting little free space is not host-disk pressure (filling a tmpfs hits its own limit, not the host disk). The guardrail now skips tmpfs/ramfs bind sources, so you should no longer need the--storage-opt size=8Gworkaround for this.Please note: I was not able to reproduce the full Wolf audio path locally, so this needs a test on your setup. Two things I would watch for if it still misbehaves:
/runat runtime and shadows the host-backed dir, and/tmp/pulse.If you can pull the latest main and retry, let me know how the
wolfpulseaudiocontainer behaves. Leaving the issue open until you confirm.@paulzzh commented on GitHub (Jun 5, 2026):
It works.
It looks like the
wolfcontainer, which is usinghostnetworking, has no network configuration at all. That means it has no network connectivity.logs of
wolfpulseaudiologs of
wolfgenerated
1000.confwolf@paulzzh commented on GitHub (Jun 5, 2026):
@JBailes commented on GitHub (Jun 5, 2026):
@paulzzh Should have fixed this.
@paulzzh commented on GitHub (Jun 5, 2026):
The network has been fixed. Test Ball now displays correctly, but the Wolf UI is still just a black screen.
@JBailes commented on GitHub (Jun 5, 2026):
@paulzzh Pushed a fix for that.
@JBailes commented on GitHub (Jun 6, 2026):
Argh, another script closed this. Anyways, waiting on your verification @paulzzh
@paulzzh commented on GitHub (Jun 6, 2026):
Wolf UI works. 👍🎉 Both the audio and the video are perfect.

There is another issue: the container cannot shutdown gracefully. It usually times out, and I have to
pct enterit manually andkill 1to stop it.@JBailes commented on GitHub (Jun 6, 2026):
I'd really like more information there, I wasn't able to successfully replicate this on my Proxmox host.
One of the issues I run into is I'm actually having to write two command paths: One for lxc, and one for proxmox. Most of my testing occurs directly on LXC rather than Proxmox. I suspect the issue you are having is specific to pve, and I'm trying to sort out what it is.
@paulzzh commented on GitHub (Jun 6, 2026):
run
docker stop 6445b6ab5b15and it blocks@JBailes commented on GitHub (Jun 7, 2026):
Pushed a PR that should fix this.
@paulzzh commented on GitHub (Jun 7, 2026):
Everything is working on Proxmox.