mviereck/x11docker

What is x11docker doing differently?

atar-axis opened this issue · 2 comments

Hey! I am having a problem and I hope one of the experts here can help me.

Having a host with Nvidia drivers, and one with mesa drivers.
x11docker with --hostdisplay runs fine on both. But sharing the following does not when running podman directly, at least not on the nvidia machine (on the other it works):

  --env DISPLAY \
  --env XAUTHORITY \
  --env XSOCKET \
  --env XDG_RUNTIME_DIR \

On the nvidia host podman complains about missing fbConfig or visuals:

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)
qt.glx: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

So, what is x11docker doing differently?
Also tried to run x11docker first and then shared with the container what --printenv prints. Same thing, works on my machine but not on the nvidia machine.

I tried to set -x in x11docker to see what it does but man, is that complex!

Found the issue, for whatever reason I had to install the nvidia-384 drivers inside the docker as well.
Any idea why that is? Btw, xClock worked even without.

Great that you found the solution yourself!