mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #40] pulseaudio container errors #24
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#24
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 @solipsist01 on GitHub (Aug 30, 2023).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/40
I'm happily running gow for months now :)
I thought, it would be nice to have multiple applications, and also work without a dummy plug, so i'm giving wolf a spin.
I'm running debian bookworm
Consider the following compose (just a copy / paste from the docs :))
Wolf starts. i can connect with moonlight etc, and also the pin stuff worked :)
the logging from the wolf container looks like this:
Seems that wolf cannot connect to pulseaudio.
This is the log listing of the pulseaudio container.
The reason wolf cannot connect to pulse audio, is because the pulseaudio container doesn't seem to run properly ?
The container does keep running, however.
When i run the firefox app from moonlight, this is the error log from the Wolf container:
Is there something i'm doing wrong ?
@ABeltramo commented on GitHub (Sep 4, 2023):
You are right, the error at the end "
Failed to connect: Connection refused" is clearly an issue with PulseAudio.The container will complain about stuff, those error messages in the logs of pulse are absolutely normal and expected; as long as the container is up and running everything should be fine.
There are a couple of things you can check:
XDG_RUNTIME_DIR, do you seepulse-socketwhen callingls -la /tmp/sockets?WOLF_LOG_LEVEL=DEBUG@solipsist01 commented on GitHub (Oct 12, 2023):
So, i finally had some free time :)
It looks like the Wolf container starts the wolfpulseaudio container with the wrong environmental variables.
it should be "XDG_RUNTIME_DIR=/tmp/sockets"
it seems it makes two serperate vars.
@ABeltramo commented on GitHub (Oct 12, 2023):
Well well, you are absolutely right, we are passing two env variables instead of doing
XDG_RUNTIME_DIR=<<runtime_dir>>!I guess that's working because we still mount
/tmp/socketsinto/tmp/pulse/which is the default folder in our custom pulseaudio container.I still don't see how this is not working for you though:
/tmp/sockets:/tmp/pulse:rwwhich seems to be missing from yourVolumesdefinition, for some reason../tmp/sockets/pulse-socketwhich should be there if you've correctly mounted it in the Wolf container.Do you ever get the line
[PULSE] Pulse connection readyin Wolf?@solipsist01 commented on GitHub (Oct 14, 2023):
i got pulse working. when wolf starts the pulseaudio container, /tmp/sockets is now mounted into /tmp/pulse inside the container, and it connects! :)
i activated the pin, and get presented the apps within moonlight.
however, when i launch an application, i get an RTSP handshake error 10054
both when the app is first created, as well as a resume afterwards, when everything exists.
i'm on the same network as the server. no firewall rules or anything, and container is running in host networking mode.
with GOW / Moonshine i don't had RTSP errors going on :), so i'm pretty sure it's not network related
and, i would say rtsp does infact receives data, considering the commands it receives.
What obvious thing am i missing here? :)
This is logs from a 'resume'
This is the actual docker-compose.yml file content:
docker inspect wolf
the pulse audio log:
@ABeltramo commented on GitHub (Oct 15, 2023):
What have you changed? Are you running the pulse container manually? Wolf should try and set that up automatically when failing to connect to pulseaudio.
This has been reported by others on Discord but I'm not able to replicate it. Which Moonlight client are you using? Could you please also lower down the
WOLF_LOG_LEVELtoTRACEand paste the RTSP messages that Wolf receives?@solipsist01 commented on GitHub (Oct 16, 2023):
this morning, i wanted to do a trace
now it's working flawlessly
i really don't understand why, though, i hate that.
if i get it again, i will definately provide the trace.
to get pulse working, i did alot of trial and error. so i'm not 100% sure what hit the spot.
i removed all files which are put on several locations. (i was cleaning the config dir only before that)
there's files in the config dir, the /tmp/sockets dir, as well as /bin/something. i tried to cleanout everything, and then it worked.
perhaps some leftovers from GOW or something, or an old version of a toml i don't know :)
@Rikiar73574 commented on GitHub (Feb 1, 2024):
just in case, i am facing the same issue and nothing is really working for me.
@royaltongue commented on GitHub (Mar 9, 2025):
Hi, I'm also running into this issue, here's the trace log
Trace Log.txt