container-images VS nvidia-docker

FROM tensorflow/tensorflow:1.15.5-gpu-py3 # Handle Nvidia public key update and update repositories for Ubuntu 18.x. #https://github.com/sangyun884/HR-VITON/issues/45 # reference: https://jdhao.github.io/2022/05/05/nvidia-apt-repo-public-key-error-fix/ RUN rm /etc/apt/sources.list.d/cuda.list RUN rm /etc/apt/sources.list.d/nvidia-ml.list RUN apt-key del 7fa2af80 # Additional reference: https://gitlab.com/nvidia/container-images/cuda/-/issues/158 RUN export this_distro="$(cat /etc/os-release | grep '^ID=' | awk -F'=' '{print $2}')" \ && export this_version="$(cat /etc/os-release | grep '^VERSION_ID=' | awk -F'=' '{print $2}' | sed 's/[^0-9]*//g')" \ && apt-key adv --fetch-keys "https://developer.download.nvidia.com/compute/cuda/repos/${this_distro}${this_version}/x86_64/3bf863cc.pub" \ && apt-key adv --fetch-keys "https://developer.download.nvidia.com/compute/machine-learning/repos/${this_distro}${this_version}/x86_64/7fa2af80.pub" # get the latest version of OpenCV RUN apt-get update && \ DEBIAN_FRONTEND=noninteractive \ apt-get install -y -qq \ wget git libopencv-dev RUN python -m pip install --upgrade pip && \ pip install matplotlib opencv-python==4.5.4.60 Pillow scipy \ azure-eventhub azure-eventhub-checkpointstoreblob-aio ipykernel WORKDIR /

As far as I can see, the way Google Chrome developers chose to support hardware acceleration under Linux is through Vulkan (here and here) According to Nvidia, there's no official support for Vulkan inside Docker. Although it seems that FAQ hasn't been updated because I was able to find a Docker container with Vulkan support here.

Looking forward to the CUDA containers getting released!

# Based on https://gitlab.com/nvidia/container-images/l4t-base/-/blob/master/Dockerfile.l4t # https://github.com/dusty-nv/jetson-containers/blob/master/Dockerfile.ros.foxy # https://github.com/codustry/jetson-containers/blob/master/Dockerfile.ros.foxy ARG L4T_MINOR_VERSION=5.0 FROM codustry/ros:foxy-ros-base-l4t-r32.${L4T_MINOR_VERSION} # # ZED Jetson # https://github.com/stereolabs/zed-docker/blob/master/3.X/jetpack_4.X/devel/Dockerfile # ARG ZED_SDK_MAJOR=3 ARG ZED_SDK_MINOR=5 ARG JETPACK_MAJOR=4 ARG JETPACK_MINOR=5 #This environment variable is needed to use the streaming features on Jetson inside a container ENV LOGNAME root ENV DEBIAN_FRONTEND noninteractive RUN apt-get update -y && apt-get install --no-install-recommends lsb-release wget less udev sudo apt-transport-https build-essential cmake openssh-server libv4l-0 libv4l-dev v4l-utils binutils xz-utils bzip2 lbzip2 curl ca-certificates libegl1 python3 -y && \ echo "# R32 (release), REVISION: 5.0" > /etc/nv_tegra_release ; \ wget -q --no-check-certificate -O ZED_SDK_Linux_JP.run https://download.stereolabs.com/zedsdk/${ZED_SDK_MAJOR}.${ZED_SDK_MINOR}/jp${JETPACK_MAJOR}${JETPACK_MINOR}/jetsons && \ chmod +x ZED_SDK_Linux_JP.run ; ./ZED_SDK_Linux_JP.run silent skip_tools && \ rm -rf /usr/local/zed/resources/* \ rm -rf ZED_SDK_Linux_JP.run && \ rm -rf /var/lib/apt/lists/* #This symbolic link is needed to use the streaming features on Jetson inside a container RUN ln -sf /usr/lib/aarch64-linux-gnu/tegra/libv4l2.so.0 /usr/lib/aarch64-linux-gnu/libv4l2.so # # Configure Enviroment for ROS RUN echo 'source /opt/ros/foxy/install/setup.bash' >> ~/.bashrc # RUN echo "source /opt/ros/eloquent/setup.bash" >> ~/.bashrc RUN echo 'source /usr/share/colcon_cd/function/colcon_cd.sh' >> ~/.bashrc # RUN echo "export _colcon_cd_root=~/ros2_install" >> ~/.bashrc # echo $LD_LIBRARY_PATH RUN echo 'export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-10.2/targets/aarch64-linux/lib/stubs:/opt/ros/foxy/install/lib' >> ~/.bashrc WORKDIR /root/Downloads RUN wget https://developer.nvidia.com/embedded/L4T/r32_Release_v5.0/T186/Tegra186_Linux_R32.5.0_aarch64.tbz2 RUN tar xf Tegra186_Linux_R32.5.0_aarch64.tbz2 RUN cd Linux_for_Tegra && \ sed -i 's/config.tbz2\"/config.tbz2\" --exclude=etc\/hosts --exclude=etc\/hostname/g' apply_binaries.sh && \ sed -i 's/install --owner=root --group=root \"${QEMU_BIN}\" \"${L4T_ROOTFS_DIR}\/usr\/bin\/\"/#install --owner=root --group=root \"${QEMU_BIN}\" \"${L4T_ROOTFS_DIR}\/usr\/bin\/\"/g' nv_tegra/nv-apply-debs.sh && \ sed -i 's/LC_ALL=C chroot . mount -t proc none \/proc/ /g' nv_tegra/nv-apply-debs.sh && \ sed -i 's/umount ${L4T_ROOTFS_DIR}\/proc/ /g' nv_tegra/nv-apply-debs.sh && \ sed -i 's/chroot . \// /g' nv_tegra/nv-apply-debs.sh && \ ./apply_binaries.sh -r / --target-overlay RUN rm -rf Tegra210_Linux_R32.4.4_aarch64.tbz2 && \ rm -rf Linux_for_Tegra && \ echo "/usr/lib/aarch64-linux-gnu/tegra" > /etc/ld.so.conf.d/nvidia-tegra.conf && ldconfig WORKDIR /usr/local/zed ENV CUDA_HOME=/usr/local/cuda WORKDIR /root/ros2_ws/src/ RUN source /opt/ros/foxy/install/setup.bash && cd ../ && colcon build --symlink-install RUN git clone https://github.com/stereolabs/zed-ros2-wrapper.git RUN git clone https://github.com/ros/diagnostics.git && cd diagnostics && git checkout foxy WORKDIR /root/ros2_ws RUN source /opt/ros/foxy/install/setup.bash && source $(pwd)/install/local_setup.bash && rosdep update && \ rosdep install --from-paths src --ignore-src -r --rosdistro ${ROS_DISTRO} -y && \ colcon build --symlink-install --cmake-args " -DCMAKE_BUILD_TYPE=Release" " -DCMAKE_LIBRARY_PATH=/usr/local/cuda/lib64/stubs" " -DCUDA_CUDART_LIBRARY=/usr/local/cuda/lib64/stubs" " -DCMAKE_CXX_FLAGS='-Wl,--allow-shlib-undefined'" && \ echo source $(pwd)/install/local_setup.bash >> ~/.bashrc && \ source ~/.bashrc

That leaves Flatcar and Clear Linux - both of which happen to at least have documentation for installing/running Nvidia drivers and CUDA. Flatcar has this repository from Nvidia, and I've also found this project called forklift which will supposedly handle auto-updating the kernel modules for you. The Clear Linux docs also seem to include a method to auto-rebuild the modules with kernel upgrades, though it does say that the driver version needs to be updated manually, which honestly almost sounds preferable considering how finicky Nvidia drivers can be on Linux. Clear Linux also has several other tutorials/guides that appear to try and market it for things like machine learning, which leads me to believe that Nvidia gpus would hopefully work decently on it.

To add CUDA I plan on adding the stuff from this Docker script.

You can use the cuda dockerfile as reference: https://gitlab.com/nvidia/container-images/cuda/-/blob/master/Dockerfile

However, getting Nvidia to work was much more complicated. Now, I am not a container expert, so a lot of it was because of my unfamiliarity with the technology. At first, I had to get nvidia-container-toolkit using CentOS package. The test containers given in the instructions here worked fine. However, I soon understood that nvidia-container-toolkit requires basing the image on nvidia official containers or going through this and figure out how to create a custom container. Most documentation online seemed to be about nvidia-docker or just covered the install portion of nvidia-container-toolkit. There was almost nothing available on how to create a custom image. After some digging around and copying and pasting (I still don't understand some of it), I was able to create a container with nvidia-smi, and other cuda commands working.

https://gitlab.com/nvidia/container-images/cuda/-/issues/109#note_503061879

Nvidia Docker on GitHub

Here's where I found discussion regarding this https://github.com/NVIDIA/nvidia-docker/issues/1671

I found the Faq, looks like Windows isn't supported which might indicate why I had this problem earlier. I might need to dual boot my machine if it won't work with WSL which I don't see mentioned in either page. WSL Cuda instructions found this I'll give it a try.

Arc has linux kernel support from 6.0, been using an A770 with tdarr for a few months. Super solid and no issues like the nvidia docker toolkit just losing the GPU. The workaround doesn't hold for long - https://github.com/NVIDIA/nvidia-docker/issues/1730 It is one of the reasons I went with Intel over waiting for a low end 40 series. The other was I that basically stole it for $199. So far Plex is the only thing that doesn't work with Arc and all the HW transcoding falls on the iGPU. Knowing how they prioritize things nobody wants, Arc support and AV1 transcoding will be added when 16th gen Intel CPUs are released.

I use ubuntu with wsl2 under windows 11. I want to learn how to get GPU-accelerated computing working. My ASUS laptop has a NVIDIA graphics card as well as a built in Intel. Please ask me any needed questions and then tell me the steps I need to get this working? SOFTWARE DEVELOPER Thanks for sharing that information. Can you please confirm if you have already installed NVIDIA drivers on your Windows 11 system? If not, you'll need to install the appropriate NVIDIA drivers for your GPU in order to enable GPU acceleration. Additionally, what is your end goal is with GPU accelerated computing? yes I have the NVIDIA control panel installed. SOFTWARE DEVELOPER Great. To enable GPU acceleration in WSL2, you'll need to follow these steps: First, confirm you are running Windows 11 build 20145 or later, and have WSL2 installed and configured to use Ubuntu. Download the NVIDIA Linux driver for your GPU from the official NVIDIA Linux download page https://www.nvidia.com/Download/index.aspx. Install the latest NVIDIA driver, including the NVIDIA Docker plugin. You can follow instructions on the NVIDIA Docker plugin GitHub page (https://github.com/NVIDIA/nvidia-docker). Install the CUDA toolkit and cuDNN library. Once you've installed the NVIDIA driver successfully, you can download the CUDA toolkit and cuDNN library (if applicable) from the official NVIDIA CUDA download page https://developer.nvidia.com/cuda-downloads. Install the NVIDIA Container Toolkit. NVIDIA Container Toolkit is a nifty package that provides a set of tools for GPU-accelerated container deployments. You can find installation instructions and a getting started guide on the NVIDIA Container Toolkit GitHub page https://github.com/NVIDIA/nvidia-docker. Test the installation by running a TensorFlow or PyTorch script that uses the GPU for accelerated computing. Check if the GPU is recognized and being used in the output of the script. Once you've successfully followed these steps, you should have GPU-accelerated computing environments in WSL2. Hope that helps! Let me know if you have any other questions. yes to question #1. On #2, do I download the Game Ready driver or the Studio Driver. I don't play games as I'm a software devevloper but want accelerated graphics for development or data science purposes. SOFTWARE DEVELOPER Great to hear that you have WSL2 set up on your system. Regarding your question, you should download the Studio Driver version, as it's optimized for professional workloads, including data science and software development. The Game Ready version is optimized for gaming and might not always provide the best performance for non-gaming workloads. Once you have downloaded the Studio Driver for your GPU, follow the instructions provided by the driver installer to complete the installation process. Let me know if you have any further questions! Would you clarify #3? Is the NVIDIA Docker plugin included with the NVIDIA driver install? Or is it a separate install. I have Docker for Windows installed and working in WSL2. SOFTWARE DEVELOPER Sure, I'd be happy to clarify. The NVIDIA Docker plugin is an additional package that needs to be installed separately from the NVIDIA drivers. The plugin provides a convenient way for creating and running GPU-accelerated Docker containers in your system. To install the NVIDIA Docker plugin, follow the instructions on the NVIDIA Docker plugin GitHub page (https://github.com/NVIDIA/nvidia-docker). Note that the plugin is only compatible with Docker CE (Community Edition) or Docker EE (Enterprise Edition) on Linux-based systems, and does not work on Docker for Windows. Once you've installed the plugin, you can use it to run GPU-accelerated containers with Docker. It's worth noting that the NVIDIA Docker plugin requires access to your host system's NVIDIA GPU, so you'll need to ensure that your GPU has been correctly installed and recognized by your system. Hope that answers your question. Let me know if you have any additional questions!

Im trying to determine how to troubleshoot & resolve the HW transcoding, but based on my testing Im assuming its some change to the NVIDIA toolkit https://github.com/NVIDIA/nvidia-docker

NVIDIA Container Toolkit

So I am in the initial planning stages of setting up a new unraid server. Looking at picking up an SC846 24bay 4u chassis. I've got a Gigabyte Aorus mb with an AMD 5950x, 32gb of ddr4 (adding more as needed) and an nvidia 3070ti. I plan on getting an LSI 8i for the drives and leaves room for expansion server plans. My goal is to have plex setup via docker and utilize the gpu transcoding to offload the cpu work. I also want to setup vms or a vm server to essentially also have a "gaming server" mainly for me and the kids. This means down the road I would be adding another GPU to split up with other users. Im trying to allow for a max of 4 people while also still allowing plex to transcode as needed. Now I know there's other ways to do this but I dont feel like splitting this up into multiple systems unless I have to. So really just trying to see if this might be possible. My worry is that in order to make the gpu available to the plex docker I have to setup an nvidia container. https://github.com/NVIDIA/nvidia-docker