Closed gaeljw closed 1 year ago
Exactly what is wrong? Are you referring to the pkill statements? Those are part of the script to remove uneccesary processes that are spawned by Zwift.
On Thu, Jan 26, 2023, 22:03 Gaël Jourdan-Weil @.***> wrote:
I'm getting the following output logs when running the container manually, not sure how to troubleshoot 👍
$ docker run --rm --privileged -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v /run/user/$UID/pulse:/run/user/1000/pulse -v $ZWIFT_HOME:/home/user/Zwift $VGA_DEVICE_FLAG $IMAGE:$VERSION
...
echo 'starting zwift...'
wine64 start ZwiftLauncher.exe
0050:err:ole:start_rpcss Failed to start RpcSs service
wine64 start RunFromProcess-x64.exe ZwiftLauncher.exe ZwiftApp.exe
pgrep ZwiftApp.exe
Waiting for zwift to start ...
echo 'Waiting for zwift to start ...'
sleep 1
0184:err:ole:CoGetContextToken apartment not initialised
pgrep ZwiftApp.exe
echo 'Killing uneccesary applications'
pkill ZwiftLauncher
Killing uneccesary applications
pkill MicrosoftEdgeUp
pkill ZwiftWindowsCra
Any idea in which direction I should look for help?
— Reply to this email directly, view it on GitHub https://github.com/netbrain/zwift/issues/13, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTNCZBJR6LYAAWRX4V5VLWULRCPANCNFSM6AAAAAAUH6WBQU . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Look's like wine doesn't run? What I observe is that the container exits after these logs, without more information. No Zwift, no window, nothing. 🤷♂️
Can you give me some information about your system? Os, xorg/Wayland? Graphics card etc..
Also does the process hang? I.e does docker ps show anything after you start Zwift or does it simply exit by itself?
On Fri, Jan 27, 2023, 07:13 Gaël Jourdan-Weil @.***> wrote:
Look's like wine doesn't run? What I observe is that the container exits after these logs, without more information. No Zwift, no window, nothing. 🤷♂️
— Reply to this email directly, view it on GitHub https://github.com/netbrain/zwift/issues/13#issuecomment-1406066842, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTNC3LSNQMUAAHSGERQBTWUNRQZANCNFSM6AAAAAAUH6WBQU . You are receiving this because you commented.Message ID: @.***>
Sure, it's a Linux Fedora 36, I believe it's Gnome with Wayland though I'd have to double check. I will also try on a Xorg to troubleshoot.
The process does not hang, the container simply exit by itself.
I'll try to run the same outside the container as well to troubleshoot and see if I get more details.
Too me it sounds like there is an issue in creating the viewport for rendering zwift. So maybe it's a wayland issue, driver issue, or unsupported graphics card?
For wayland please see: https://unix.stackexchange.com/questions/330366/how-can-i-run-a-graphical-application-in-a-container-under-wayland
If you have a nvidia card, you need the nvidia-container-toolkit, for other cards they "should" work by making them accesible through --device /dev/dri.
Feel free to re-open if the abovementioned is not the case.
Also, this looks like an interesting project that this could probably benefit from.
Indeed, I just tested with a Xorg laptop and it works great :)
Yeah most likely the container is missing Wayland support. Feel free to add it 😊 🙏
On Tue, Jan 31, 2023, 12:14 Gaël Jourdan-Weil @.***> wrote:
Indeed, I just tested with a Xorg laptop and it works great :)
— Reply to this email directly, view it on GitHub https://github.com/netbrain/zwift/issues/13#issuecomment-1410174421, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTNC4XA6TB527LJ3PUAETWVDXZXANCNFSM6AAAAAAUH6WBQU . You are receiving this because you modified the open/close state.Message ID: @.***>
I'm getting the following output logs when running the container manually, not sure how to troubleshoot :+1:
Any idea in which direction I should look for help?