netbrain / zwift

Easily zwift on linux
The Unlicense
242 stars 27 forks source link

[HELP] Container crashing at startup #161

Open aleduc-cyb opened 1 day ago

aleduc-cyb commented 1 day ago

Checklist

Describe the issue

After running zwift container starts but fails within 10 seconds.

I saw the XDG_RUNTIME_DIR error and tried setting it up to my current environment variable but the errors at the end are still there. Tried with and without external display.

Thanks a lot for your help :)

Distribution Details

Reproduction steps

  1. Run zwift command
netbrain commented 1 day ago

01e4:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.

This usually means that it's having trouble accessing your gpu. I take it you have a intel or amd gpu?

@sHedC do you have any suggestions?

aleduc-cyb commented 1 day ago

Thanks for the feedback! GPU is Intel Iris Xe.

netbrain commented 1 day ago

Try running glxgears like mentioned here

https://github.com/netbrain/zwift/issues/88#issuecomment-2094692406

If glxgears isn't working then you probably have a driver issue

aleduc-cyb commented 1 day ago

I got Error: couldn't open display :0 with glxgears. Tried to reinstall the drivers but did not manage to have significant change. I will continue debugging but if you have some further idea let me know :)

netbrain commented 1 day ago

Does glxgears work on the host? And not inside the container?

On Sun, Sep 22, 2024, 15:53 Alexis DUCREUX @.***> wrote:

I got Error: couldn't open display :0 with glxgears. Tried to reinstall the drivers but did not manage to have significant change. I will continue debugging but if you have some further idea let me know :)

— Reply to this email directly, view it on GitHub https://github.com/netbrain/zwift/issues/161#issuecomment-2366800082, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTNC6IYJRPB4LRW7UZYETZX3DW5AVCNFSM6AAAAABOUJX7AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHAYDAMBYGI . You are receiving this because you commented.Message ID: @.***>

sHedC commented 1 day ago

Its a bit weird can you check that you see /dev/dri/renderD*, if so try running xhost + first then run glxgears. Also can you see what DISPLAY holds in a terminal.

I wonder if glxgears is not running that there is a problem with missing mesa drivers?

aleduc-cyb commented 1 day ago

I can see /dev/dri/renderD128 on the host. Running xhost before does not seem to have an effect. No problem with glxgears on the host. DISPLAY is :0 on the host and within the container.

netbrain commented 1 day ago

Might be the container that's missing your particular driver. Do you know what package that provides it?

On Sun, Sep 22, 2024, 16:22 Alexis DUCREUX @.***> wrote:

I can see /dev/dri/renderD128 on the host. Running xhost before does not seem to have an effect. No problem with glxgears on the host. DISPLAY is :0 on the host and within the container.

— Reply to this email directly, view it on GitHub https://github.com/netbrain/zwift/issues/161#issuecomment-2366811383, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTNC4UWGVZ7SUOFY5DL73ZX3HDVAVCNFSM6AAAAABOUJX7AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHAYTCMZYGM . You are receiving this because you commented.Message ID: @.***>

sHedC commented 1 day ago

Ok reading through seems like all is ok, I think the errors at the end are quite often there but need to check as been a while since I looked.

I don't have an INTEL chip so can't run any tests only have AMD/ NVIDIA.

Just one thing to try that I can think of can you run xhost + first then run zwift in the same terminal. as you are running docker i don't see any other permission error but also don't see any xhost permission failures so it a bit strange.

I will also check the XAuthority volume, it is passing it through to the user alexis not user but that could be right as I can't remember now so will have a look at that.

sHedC commented 1 day ago

Might be the container that's missing your particular driver. Do you know what package that provides it? On Sun, Sep 22, 2024, 16:22 Alexis DUCREUX @.> wrote: I can see /dev/dri/renderD128 on the host. Running xhost before does not seem to have an effect. No problem with glxgears on the host. DISPLAY is :0 on the host and within the container. — Reply to this email directly, view it on GitHub <#161 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTNC4UWGVZ7SUOFY5DL73ZX3HDVAVCNFSM6AAAAABOUJX7AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHAYTCMZYGM . You are receiving this because you commented.Message ID: @.>

That is a valid point it would rely on the dri and mesa drivers I think. But I don;t think there is any difference between the AMD or Intel mesa/ dri drivers its "mesa-dri-drivers" I will check that out.

aleduc-cyb commented 1 day ago

From what I understand, the package is intel-i915-dkms (my host version is 1.23.10.72.231129.74+i110-1)

Might be the container that's missing your particular driver. Do you know what package that provides it? On Sun, Sep 22, 2024, 16:22 Alexis DUCREUX @.> wrote: I can see /dev/dri/renderD128 on the host. Running xhost before does not seem to have an effect. No problem with glxgears on the host. DISPLAY is :0 on the host and within the container. — Reply to this email directly, view it on GitHub <#161 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTNC4UWGVZ7SUOFY5DL73ZX3HDVAVCNFSM6AAAAABOUJX7AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHAYTCMZYGM . You are receiving this because you commented.Message ID: @.>