selkies-project / docker-nvidia-egl-desktop Goto Github PK

KDE Plasma Desktop container designed for Kubernetes with direct access to the GPU with EGL using VirtualGL and Vulkan for GPUs with WebRTC and HTML5, providing an open-source remote cloud graphics or game streaming platform. Does not require /tmp/.X11-unix host sockets or host configuration.

Home Page: https://github.com/selkies-project/docker-nvidia-egl-desktop/pkgs/container/nvidia-egl-desktop

License: Mozilla Public License 2.0

Dockerfile 84.53% Shell 15.47%

nvidia-docker nvidia docker-image docker html5 opengl ubuntu gpu nvidia-gpu kubernetes

docker-nvidia-egl-desktop's People

Contributors

Stargazers

Watchers

docker-nvidia-egl-desktop's Issues

Unity 3d-Rendering app does not recognize the display/desktop in Docker env

I'm trying to run a headless render app (Unity3d) inside docker container.
Tried vglrun tool as well, but it doesn't work.
The app logs ending with Desktop is 0 x 0 @ 0 Hz.

It does work on the normal ubuntu-desktop (not dockerized).
Works with emulation tool xvfb-run --auto-servernum --server-args='-screen 0 640x480x24' ./app.x86_64, but it doesn't use GPU

Do you have any suggestions? Thanks

The screen locker is broken and unlocking is not possible anymore

When using NOVNC_ENABLE=true we get the screen locked after some time showing a black screen with The screen locker is broken and unlocking is not possible anymore does anyone knows how to get passed this?

Using: ghcr.io/selkies-project/nvidia-egl-desktop:latest

How to have GPU-based rendering in docker console?

Hi,

Thanks for this great project. It helps a lot and I really appreciate it. I follow the instructions to run that docker container and log in through webVNC. I can confirm that the GPU-based is working as I got the following output:

user@351d9e1b605d:/opt/VirtualGL/bin$ ./glxspheres64 
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
GLX FB config ID of window: 0x11 (8/8/8/0)
Visual ID of window: 0x21
Context is Direct
OpenGL Renderer: NVIDIA GeForce RTX 3090/PCIe/SSE2
1041.901382 frames/sec - 1162.761942 Mpixels/sec
1005.491010 frames/sec - 1122.127967 Mpixels/sec

However, when I try to use login to that container through docker console instead, the rendering seems to happen on CPU instead.

This is how I log in to the container through docker console:

docker exec -it <container_id> /bin/bash

And the output for the same command:

user@351d9e1b605d:/opt/VirtualGL/bin$ ./glxspheres64
Polygons in scene: 62464 (61 spheres * 1024 polys/spheres)
GLX FB config ID of window: 0x13d (8/8/8/0)
Visual ID of window: 0x3d0
Context is Direct
OpenGL Renderer: llvmpipe (LLVM 12.0.0, 256 bits)
71.574763 frames/sec - 79.877436 Mpixels/sec

I understand there might be some extra setups if I go through the console instead of webVNC. Can you help me with a pointer?

LMK if you need more information from me.

ASK: how to start single window application

Hello, I love this repo. thanks so much.

I'm trying to start a single X client instead of the full xfce4-session. So far I've tried with xstart but no result so far. any ideas?

My end goal is to run:
startx /usr/bin/qemu-system-x86_64 ...

Question regarding building a pod based on this image

Dear @ehfd, thank you so much for this great repo. You really saved my life!

But I have a few questions regarding the images:

As I'm training some deep learning models using Unity simulation (it has some renderings and visual observations), the remote server with a GUI would be truly helpful. In this case, if I build my pod/job to train my networks with your configuration YAML files: xgl.yml or egl.yml (both provide Vulkan and OpenGL), I don't need to install or deal with anything like Xvfb right? And from the document, I could directly use my (client) web browser to open the UI similar to VNC?
However, when using these two YAML files to create my pod, both failed with the status CreateContainerConfigError. Do I need to modify anything in your example YAML files? Or is this error caused by yesterday's Nautilus broken or corruption issues?

Thank you again. Look forward to your reply!

NVIDIA Drivers required with nvidia-headless

Hello

I have created an image which would not have been possible without the work you have done here (and the gstreamer interface) - Amazing job.

I have discovered that EGL is only possible with /dev/dri exposed within the container unless the Nvidia drivers are installed in the same way as you do with the GLX variant.

I'm happy to submit a PR to add this on, but I'll be mostly giving your own code back to you. I wanted to check what you wanted first.

Rob

Instruction to test

I am testing this repository for remote desktop with GPU, using this g3.medium from https://docs.jetstream-cloud.org/general/vmsizes/#jetstream2-gpu.

This instance has Nvidia driver 525.60.13. As per support matrix, this gpu (A100) doesnt support NVENC, so I replaced WEBRTC_ENCODER with vp9enc. Here is the full docker command:

docker run --gpus 1 -it --tmpfs /dev/shm:rw -e TZ=UTC -e SIZEW=1920 -e SIZEH=1080 -e REFRESH=60 -e DPI=96 -e CDEPTH=24 -e PASSWD=mypasswd -e WEBRTC_ENCODER=vp9enc -e BASIC_AUTH_PASSWORD=mypasswd -p 8080:8080 ghcr.io/selkies-project/nvidia-egl-desktop:latest

here is the output of the this:

2023-01-19 19:32:05,876 INFO Set uid to user 1000 succeeded
2023-01-19 19:32:05,878 INFO supervisord started with pid 1
2023-01-19 19:32:06,882 INFO spawned: 'entrypoint' with pid 7
2023-01-19 19:32:06,885 INFO spawned: 'pulseaudio' with pid 8
2023-01-19 19:32:06,888 INFO spawned: 'selkies-gstreamer' with pid 9
2023-01-19 19:32:06,898 INFO reaped unknown pid 15 (exit status 1)
2023-01-19 19:32:06,980 INFO reaped unknown pid 21 (exit status 1)
2023-01-19 19:32:06,980 INFO reaped unknown pid 24 (exit status 1)
2023-01-19 19:32:06,980 INFO reaped unknown pid 27 (exit status 1)
2023-01-19 19:32:06,981 INFO reaped unknown pid 31 (exit status 1)
2023-01-19 19:32:06,981 INFO reaped unknown pid 36 (exit status 1)
2023-01-19 19:32:06,981 INFO reaped unknown pid 39 (exit status 1)
2023-01-19 19:32:06,981 INFO reaped unknown pid 43 (exit status 1)
2023-01-19 19:32:06,988 INFO reaped unknown pid 46 (exit status 1)
2023-01-19 19:32:07,900 INFO success: entrypoint entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-19 19:32:07,900 INFO success: pulseaudio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-19 19:32:07,901 INFO success: selkies-gstreamer entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-01-19 19:32:07,931 INFO reaped unknown pid 65 (exit status 1)
2023-01-19 19:32:07,931 INFO reaped unknown pid 62 (exit status 1)
2023-01-19 19:32:07,931 INFO reaped unknown pid 69 (exit status 1)
2023-01-19 19:32:10,103 INFO reaped unknown pid 144 (exit status 0)
2023-01-19 19:32:10,239 INFO reaped unknown pid 151 (exit status 0)
2023-01-19 19:32:10,752 INFO reaped unknown pid 165 (exit status 0)
2023-01-19 19:32:10,962 INFO reaped unknown pid 254 (exit status 0)
2023-01-19 19:32:12,550 INFO reaped unknown pid 333 (exit status 0)

When I login with the provided user name and password, things seem to stuck at the "Waiting for video stream" step. I am not getting any desktop, even if I wait for 10 minutes. Am I missing some steps from instructions?

And these are the status logs from the client, if they are of any help:

[11:33:17] [webrtc] [ERROR] attempt to send data channel message before channel was open.

[11:33:19] [signalling] Connecting to server.

[11:33:21] [signalling] Registering with server, peer ID: 1

[11:33:23] [signalling] Registered with server.

[11:33:23] [signalling] Waiting for video stream.

[11:33:25] [webrtc] [ERROR] attempt to send data channel message before channel was open.

[11:33:25] [webrtc] Received incoming video stream from peer

[11:33:25] [webrtc] Received incoming audio stream from peer

[11:33:25] [webrtc] Completed ICE candidates from peer connection

[11:33:43] [webrtc] [ERROR] attempt to send data channel message before channel was open.

[11:33:46] [webrtc] [ERROR] attempt to send data channel message before channel was open.

[11:33:46] [webrtc] [ERROR] attempt to send data channel message before channel was open.

[11:33:48] [webrtc] [ERROR] attempt to send data channel message before channel was open.

No --device=/dev/dri, glxgears is not running on nvidia gpu

My host machine is ubuntu18.04 with 4 nvidia gpus. And I don't have /dev/dri node, with nvidia driver, I have /dev/nvidia0, /dev/nvidia1, /dev/nvidia2, /dev/nvidia3 instead. I can docker run, and connect vnc, but can not use gpu.

I can run glxgears, or vglrun glxgears, but not on gpu.
Command to start container is :
docker run --gpus 1 -it -e SIZEW=1920 -e SIZEH=1080 -e CDEPTH=24 -e SHARED=TRUE -e VNCPASS=vncpasswd -p 5901:5901 -v "/tmp/.docker.xauth:/tmp/.docker.xauth" -e XAUTHORITY=/tmp/.docker.xauth --name vv --rm --runtime=nvidia ehfd/nvidia-egl-desktop:latest

selkies-gstream hit 100% CPU

Wishing you a Happy New Year! I've set up a node using Standard_NC16as_T4_v3 in AKS . However, we're encountering issue where the pod runs for a few minutes with CPU usage under 9% for selkies-gstream process , but then it abruptly jumps to over 100%, causing the pod to freeze again and become inaccessible . Please could you advise if there is anything that have been missing while deploying this apps within azure environment

Unable to choose node affinity

Hello,

I am trying to choose node affinity in order to specify which GPU I want to use for a specific program. Whenever I try to set the node affinity, the container gets stuck at the Pending status. Is there any way to set the node affinity / select the specific type of GPU to be used?

EDIT: Fixed! My CPU requirements were too high which made it so that no node satisfied my requirements. Thank you!

SIGKILL/SIGSTOP can not be trapped

docker-nvidia-egl-desktop/entrypoint.sh

Line 7 in f79e995

trap "echo TRAPed signal" HUP INT QUIT KILL TERM

SIGKILL/SIGSTOP can not be trapped.shellcheck

https://www.shellcheck.net/wiki/SC2173

Enhancement request - AArch64 support

Any plans to support Nvidia Jetson Orin or Xavier systems on AArch64?

Would be from Jetpack 5.x

Google Chrome with GPU

Hello, I am trying to run google-chrome with gpu acceleration, but it reports following errors.

libEGL warning: DRI2: failed to authenticate
[87:87:0115/224538.411482:ERROR:vaapi_wrapper.cc(830)] Could not get a valid VA display
[87:87:0115/224538.411770:ERROR:gpu_init.cc(523)] Passthrough is not supported, GL is egl, ANGLE is 
[87:87:0115/224538.566925:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_intel.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_radeon.so supports Vulkan 1.2, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: loader_scanned_icd_add: Driver /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so supports Vulkan 1.1, but only supports loader interface version 4. Interface version 5 or newer required to support this version of Vulkan (Policy #LDP_DRIVER_7)
Warning: Layer VK_LAYER_MESA_device_select uses API version 1.2 which is older than the application specified API version of 1.3. May cause issues.
error: XDG_RUNTIME_DIR not set in the environment.
error: XDG_RUNTIME_DIR not set in the environment.
[87:87:0115/224547.422974:ERROR:gl_display.cc(508)] EGL Driver message (Error) eglMakeCurrent: EGL_BAD_CONTEXT error: In eglMakeCurrent: Invalid EGLContext (0x3c08012326f0)

[87:87:0115/224547.459609:ERROR:gl_display.cc(508)] EGL Driver message (Error) eglMakeCurrent: EGL_BAD_CONTEXT error: In eglMakeCurrent: Invalid EGLContext (0x3c0805665a11)

Error: eglChooseConfig returned zero configs
    at Create (../../third_party/dawn/src/dawn/native/opengl/ContextEGL.cpp:53)

Error: EGL_EXT_create_context_robustness must be supported
    at Create (../../third_party/dawn/src/dawn/native/opengl/ContextEGL.cpp:67)

Despite those errors in console, google chrome reports everything works fine:

I am using following arguments, and starting it with vglrun:

  --disable-software-rasterizer
  --disable-frame-rate-limit
  --disable-gpu-driver-bug-workarounds
  --disable-gpu-driver-workarounds
  --disable-gpu-vsync
  --enable-accelerated-2d-canvas
  --enable-accelerated-video-decode
  --enable-accelerated-mjpeg-decode
  --enable-unsafe-webgpu
  --enable-features=Vulkan,UseSkiaRenderer,VaapiVideoEncoder,VaapiVideoDecoder,CanvasOopRasterization
  --disable-features=UseOzonePlatform,UseChromeOSDirectVideoDecoder
  --enable-gpu-compositing
  --enable-native-gpu-memory-buffers
  --enable-gpu-rasterization
  --enable-oop-rasterization
  --enable-raw-draw
  --enable-zero-copy
  --ignore-gpu-blocklist
  --use-gl=egl

Do you have any idea?

Thank you for this project, btw!

Will this work without i386 ?

I was wondering if I remove all i386 references and try to use only amd64 architecture, will this project still work? or does it really need all the i386 packages?

Video stream issue

Hello,

when I try using the command you gave in the repo to run an container using image,The web login works,the function works,but stuck at “waiting for video stream”,please look into this,

thank you,

Choosing a specific GPU device rendering in docker console? / VGL_DISPLAY for VirtualGL

Hi,

Thanks for this great project. It helps a lot and we really appreciate it. We follow the instructions to run that docker container and it works. How to have GPU-based rendering in docker console?

However, when we try to choose a specific GPU device rendering in docker console, it seems not work.

NVIDIA_VISIBLE_DEVICES=2 vglrun /opt/VirtualGL/bin/glxspheres64
CUDA_VISIBLE_DEVICES=2 vglrun /opt/VirtualGL/bin/glxspheres64

We try some command above, but vglrun still run on the device 1. Could you give us some advice for that?
Thank you very much.

Missing gstreamer plugins nice, webrtc, dtls, ...

Hi, thanks a lot for this repo, it's been extremely useful!

I've customized the container considerable and for some reason I get an error after running selkies-gstreamer --addr="127.0.0.1" --port="8080"

Traceback (most recent call last):
  File "/opt/conda/bin/selkies-gstreamer", line 8, in <module>
    sys.exit(main())
  File "/opt/conda/lib/python3.10/site-packages/selkies_gstreamer/__main__.py", line 527, in main
    app = GSTWebRTCApp(stun_servers, turn_servers, enable_audio, audio_channels, curr_fps, args.encoder, curr_video_bitrate, curr_audio_bitrate)
  File "/opt/conda/lib/python3.10/site-packages/selkies_gstreamer/gstwebrtc_app.py", line 83, in __init__
    self.check_plugins()
  File "/opt/conda/lib/python3.10/site-packages/selkies_gstreamer/gstwebrtc_app.py", line 654, in check_plugins
    raise GSTWebRTCAppError('Missing gstreamer plugins:', missing)
gstwebrtc_app.GSTWebRTCAppError: ('Missing gstreamer plugins:', ['nice', 'webrtc', 'dtls', 'srtp', 'rtp', 'sctp', 'rtpmanager', 'ximagesrc', 'nvcodec'])

The plugins seem to be there, any tip on what to look at I would appreciate.

ll /opt/gstreamer/lib/x86_64-linux-gnu/libgstwebrtc-1.0.so
ll /opt/gstreamer/lib/x86_64-linux-gnu/libgstwebrtc-1.0.so.0
ll /opt/gstreamer/lib/x86_64-linux-gnu/libgstwebrtc-1.0.so.0.2005.0
etc...

Choosing a specific device ID for NVIDIA GPUs

Thanks for your great job!

I have success run docker-nvidia-egl-desktop:latest.

However, I happened to this problem and failed.

I want to run Calar simulator which need to run in ubuntu 18.04.

It would be great to provide 18.04 version too.

Here is some information run in docker.

docker run --gpus 4 --device=/dev/dri:rw -it  -e SHARED=TRUE -e VNCPASS=vncpasswd -p 5901:5901 ehfd/nvidia-glx-desktop:18.04

user@b769976cec0e:~$ printf "3\nn\nx\n" | sudo /opt/VirtualGL/bin/vglserver_config

1) Configure server for use with VirtualGL (GLX + EGL back ends)
2) Unconfigure server for use with VirtualGL (GLX + EGL back ends)
3) Configure server for use with VirtualGL (EGL back end only)
4) Unconfigure server for use with VirtualGL (EGL back end only)
X) Exit

Choose:

Restrict framebuffer device access to vglusers group (recommended)?
[Y/n]
... Creating /etc/modprobe.d/virtualgl.conf to set requested permissions for
    /dev/nvidia* ...
... Attempting to remove nvidia module from memory so device permissions
    will be reloaded ...
rmmod: ERROR: Module nvidia is in use by: nvidia_uvm nvidia_modeset
... Granting write permission to /dev/nvidia-modeset /dev/nvidia-uvm /dev/nvidia-uvm-tools /dev/nvidia0 /dev/nvidia1 /dev/nvidia2 /dev/nvidia3 /dev/nvidiactl for all users ...
chmod: changing permissions of '/dev/nvidia-modeset': Read-only file system
chmod: changing permissions of '/dev/nvidia-uvm': Read-only file system
chmod: changing permissions of '/dev/nvidia-uvm-tools': Read-only file system
chmod: changing permissions of '/dev/nvidia0': Read-only file system
chmod: changing permissions of '/dev/nvidia1': Read-only file system
chmod: changing permissions of '/dev/nvidia2': Read-only file system
chmod: changing permissions of '/dev/nvidia3': Read-only file system
chmod: changing permissions of '/dev/nvidiactl': Read-only file system
chown: changing ownership of '/dev/nvidia-modeset': Read-only file system
chown: changing ownership of '/dev/nvidia-uvm': Read-only file system
chown: changing ownership of '/dev/nvidia-uvm-tools': Read-only file system
chown: changing ownership of '/dev/nvidia0': Read-only file system
chown: changing ownership of '/dev/nvidia1': Read-only file system
chown: changing ownership of '/dev/nvidia2': Read-only file system
chown: changing ownership of '/dev/nvidia3': Read-only file system
chown: changing ownership of '/dev/nvidiactl': Read-only file system
... Granting write permission to /dev/dri/card0 /dev/dri/card1 /dev/dri/card2 /dev/dri/card3 /dev/dri/card4 /dev/dri/card5 /dev/dri/card6 /dev/dri/card7 /dev/dri/card8 for all users ...
... Granting write permission to /dev/dri/renderD128 /dev/dri/renderD129 /dev/dri/renderD130 /dev/dri/renderD131 /dev/dri/renderD132 /dev/dri/renderD133 /dev/dri/renderD134 /dev/dri/renderD135 for all users ...

1) Configure server for use with VirtualGL (GLX + EGL back ends)
2) Unconfigure server for use with VirtualGL (GLX + EGL back ends)
3) Configure server for use with VirtualGL (EGL back end only)
4) Unconfigure server for use with VirtualGL (EGL back end only)
X) Exit

Choose:

Test issue.

replace noVNC to KasmVNC

kasmVNC has better support for clipborad, sound, remote files, compared to noVNC.

https://github.com/kasmtech/KasmVNC.git

how to modify the entrypoint.sh in container

Hi,
If I modified the /etc/entrypoint.sh in the container, then restart the container, the process will be less than first start, what's the problem?

user@c907d6e6b0c7:~$ ps -ef
UID PID PPID C STIME TTY TIME CMD
user 1 0 1 04:44 pts/0 00:00:00 /usr/bin/python3 /usr/bin/supervisord
user 8 1 0 04:44 pts/0 00:00:00 /bin/bash /etc/entrypoint.sh
root 29 1 0 04:44 ? 00:00:00 sshd: /usr/sbin/sshd [listener] 0 of 10-100 startups
message+ 43 1 0 04:44 ? 00:00:00 /usr/bin/dbus-daemon --system
user 105 8 51 04:44 pts/0 00:00:09 /usr/bin/java -Djava.util.logging.config.file=/opt/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048
user 106 8 0 04:44 pts/0 00:00:00 guacd -b 0.0.0.0 -f
user 161 0 2 04:44 pts/1 00:00:00 /bin/bash
user 172 161 0 04:44 pts/1 00:00:00 ps -ef

Cannot see the VNC like processes anymore, any ideas?
Thanks a lot.

NVIDIA headless drivers do not support the container

INFO:signaling:Listening on http://0.0.0.0:8080
INFO:signaling:websocket server started
INFO:webrtc_input:Resetting keyboard modifiers.
INFO:webrtc_input:starting clipboard monitor
INFO:webrtc_input:Found XFIXES version 4.0
INFO:webrtc_input:starting cursor monitor
INFO:webrtc_input:watching for cursor changes
INFO:webrtc_input:sending clipboard content, length: 34
ERROR:asyncio:Future exception was never retrieved
future: <Future finished exception=IndexError('list index out of range')>
Traceback (most recent call last):
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.10/dist-packages/selkies_gstreamer/__main__.py", line 732, in <lambda>
    loop.run_in_executor(None, lambda: gpu_mon.start())
  File "/usr/local/lib/python3.10/dist-packages/selkies_gstreamer/gpu_monitor.py", line 42, in start
    gpu = GPUtil.getGPUs()[0]
IndexError: list index out of range
INFO:signaling:Connected to ('127.0.0.1', 59490)
INFO:signaling:Registered peer '0' at ('127.0.0.1', 59490)
INFO:signaling:'0' command 'SESSION 1'
WARNING:webrtc_input:exception from fetching cursor image: <class 'Xlib.error.BadAccess'>: code = 10, resource_id = 1293, sequence_number = 20, major_opcode = 138, minor_opcode = 4
INFO:signaling:'0' command 'SESSION 1'
INFO:signaling:Connected to ('172.38.0.3', 36944)
INFO:signaling:'0' command 'SESSION 1'
INFO:signaling:Registered peer '1' at ('172.38.0.3', 36944)
INFO:signaling:'0' command 'SESSION 1'
INFO:signaling:Session from '0' (('127.0.0.1', 59490)) to '1' (('172.38.0.3', 36944))
INFO:gstwebrtc_app:starting pipeline
0:00:06.375390028    60 0x55645ad7c690 WARN     GST_ELEMENT_FACTORY gstelementfactory.c:701:gst_element_factory_make_with_properties: no such element factory "cudaupload"!
0:00:06.375402718    60 0x55645ad7c690 WARN     GST_ELEMENT_FACTORY gstelementfactory.c:701:gst_element_factory_make_with_properties: no such element factory "cudaconvert"!
0:00:06.375430511    60 0x55645ad7c690 WARN     GST_ELEMENT_FACTORY gstelementfactory.c:754:gst_element_factory_make_valist: no such element factory "nvh264enc"!
ERROR:main:Caught exception: 'NoneType' object has no attribute 'set_property'
INFO:webrtc_input:stopping clipboard monitor
INFO:webrtc_input:stopping cursor monitor
INFO: gst-python install looks OK
WARNING:webrtc_input:exception from fetching cursor image: <class 'Xlib.error.BadAccess'>: code = 10, resource_id = 1293, sequence_number = 23, major_opcode = 138, minor_opcode = 4
INFO:webrtc_input:exiting cursor monitor

selkies will not connect to the TURN forwarding port even if a coturn ip is set in the environment

selkies will not connect to the TURN forwarding port even if a coturn is set in the environment.

it will only use the coturn as a STUN server and get the container's ip address, which in my case is behind the firewall.

selkies-project / docker-nvidia-egl-desktop Goto Github PK

docker-nvidia-egl-desktop's People

Contributors

Stargazers

Watchers

Forkers

docker-nvidia-egl-desktop's Issues

Recommend Projects

Recommend Topics

Recommend Org