Seungmin Kim 2 سال پیش
والد
کامیت
b2bbc989f8
2فایلهای تغییر یافته به همراه10 افزوده شده و 2 حذف شده
  1. 8 0
      Dockerfile
  2. 2 2
      README.md

+ 8 - 0
Dockerfile

@@ -244,6 +244,7 @@ Pin-Priority: -1" > /etc/apt/preferences.d/firefox-nosnap && \
         dolphin-plugins \
         dbus-x11 \
         fcitx \
+        fcitx-frontend-qt5 \
         fcitx-module-dbus \
         fcitx-module-kimpanel \
         fcitx-module-lua \
@@ -284,6 +285,13 @@ Pin-Priority: -1" > /etc/apt/preferences.d/firefox-nosnap && \
         libgdk-pixbuf2.0-bin \
         libgtk2.0-bin \
         libgtk-3-bin \
+        libkf5baloowidgets-bin \
+        libkf5dbusaddons-bin \
+        libkf5iconthemes-bin \
+        libkf5kdelibs4support5-bin \
+        libkf5khtml-bin \
+        libkf5parts-plugins \
+        libqt5multimedia5-plugins \
         okular \
         okular-extra-backends \
         partitionmanager \

+ 2 - 2
README.md

@@ -146,9 +146,9 @@ kubectl create secret generic turn-password --from-literal=turn-password=MY_TURN
 
 ### The container does not work.
 
-Check that the [NVIDIA Container Toolkit](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html) is properly configured in the host. After that, check the environment variable `NVIDIA_DRIVER_CAPABILITIES` after starting a shell interface inside the container.
+Check that the [NVIDIA Container Toolkit](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html) is properly configured in the host. Next, check whether your host NVIDIA GPU driver is the `nvidia-headless` variant, which lacks the required display and graphics capabilities for this container.
 
-`NVIDIA_DRIVER_CAPABILITIES` should be set to `all`, or include a comma-separated list of `compute` (requirement for CUDA and OpenCL, or for the [selkies-gstreamer](https://github.com/selkies-project/selkies-gstreamer) WebRTC remote desktop interface), `utility` (requirement for `nvidia-smi` and NVML), `graphics` (requirement for OpenGL and part of the requirement for Vulkan), `video` (required for encoding or decoding videos using NVIDIA GPUs, or for the [selkies-gstreamer](https://github.com/selkies-project/selkies-gstreamer) WebRTC remote desktop interface), `display` (the other requirement for Vulkan), and optionally `compat32` if you use Wine or 32-bit graphics applications.
+After that, check the environment variable `NVIDIA_DRIVER_CAPABILITIES` after starting a shell interface inside the container. `NVIDIA_DRIVER_CAPABILITIES` should be set to `all`, or include a comma-separated list of `compute` (requirement for CUDA and OpenCL, or for the [selkies-gstreamer](https://github.com/selkies-project/selkies-gstreamer) WebRTC remote desktop interface), `utility` (requirement for `nvidia-smi` and NVML), `graphics` (requirement for OpenGL and part of the requirement for Vulkan), `video` (required for encoding or decoding videos using NVIDIA GPUs, or for the [selkies-gstreamer](https://github.com/selkies-project/selkies-gstreamer) WebRTC remote desktop interface), `display` (the other requirement for Vulkan), and optionally `compat32` if you use Wine or 32-bit graphics applications.
 
 Moreover, if you are using custom configurations, check if your shared memory path `/dev/shm` has sufficient capacity, where expanding the capacity is done by adding `--tmpfs /dev/shm:rw` to your Docker command or adding the below lines to your Kubernetes configuration file.