gklingler / docker3d Goto Github PK

according to “”if your host uses an open source driver” ，run container and exec glxgears :
[root@961d112d4b0d misc]# glxinfo | grep Open
libGL: screen 0 does not appear to be DRI2 capable
libGL: MESA-LOADER: dlopen(/usr/lib64/dri/swrast_dri.so)
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /root/.drirc: No such file or directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: Tesla V100-PCIE-16GB/PCIe/SSE2
OpenGL version string: 1.4 (2.1.2 NVIDIA 450.80.02)
OpenGL extensions:

First, thanks for pointing out "--privileged is essential for DRI support." - this saved me when trying to use Nvidia's CUDA containers to also get OpenGL working.

I'm not exactly sure of the implications of using --privileged, though it sounds like you are basically just giving the container the same privileges your user would have for device access (i.e., not necessarily root access level). That sounds reasonable to me, though some of what I read casually indicated it could be used for exploits.

Are there possibly more granular options that can be used on the horizon?

Is this solution feasible with boot2docker on OS X?