jetson-containers VS container-images

Compare jetson-containers vs container-images and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
jetson-containers container-images
10 9
1,596 -
- -
9.9 -
7 days ago -
Python
MIT License -
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

jetson-containers

Posts with mentions or reviews of jetson-containers. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-25.
  • Install ros 2 humble on jetson orin
    3 projects | /r/ROS | 25 Jun 2023
    https://github.com/dusty-nv/jetson-containers This one might be helpful
  • Should I use Docker ROS2?
    1 project | /r/ROS | 16 Jan 2023
    That's the worst solution because you lose CUDA support, if you don't use the NANO's GPU you can use a Rpi4 instead that has a more powerful CPU. Docker is the solution instead, there are ready images for Jetson: https://github.com/dusty-nv/jetson-containers
  • troubles trying to install ros2 on jetson nano
    2 projects | /r/JetsonNano | 11 Aug 2022
    Finally, if you don't want the full ros2 desktop on the nano (you may struggle with memory anyway) then jetson containers can run foxy etc with your existing jetpack version. https://github.com/dusty-nv/jetson-containers
  • Raspberry Pi4 Good Enough for SLAM?
    2 projects | /r/robotics | 19 Dec 2021
    I had to modify this dockerfile to get pangolin to work, but now it is the ORB_SLAM2_CODA portion that I cannot figure out.
  • How to build ZED 2i Camera x ROS2 Foxy x Nvidia Jetson x Ubuntu 18.04 via Docker
    7 projects | dev.to | 15 Sep 2021
    # 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
  • Trying to install opencv-cuda on Jetson nano
    1 project | /r/CUDA | 19 Aug 2021
    Have you tried looking at some jetson nano docker images? https://github.com/dusty-nv/jetson-containers
  • Should I use ROS or ROS2 to make an obstacle avoidance robot that runs SLAM and which ROS "package" should I use given my hardware (like Noetic, or kinetic or Fitzroy etc)
    1 project | /r/ROS | 15 May 2021
    Yeah, Nvidia has been very slow to release a 20.04 version, but they have provided a lot of Docker containers just for the Jetson for people to use. Here is the Nvidia dev that works on the project.
  • Newbie question: When given several containers full of demo code, how does one mix and match?
    1 project | /r/JetsonNano | 15 Apr 2021
    There are also pip wheels provided. You can easily install them into your system, even without using containers. Also, look at the l4t-ml Dockerfile, which merges some stuff from several containers, using Docker multi-stage builds.

container-images

Posts with mentions or reviews of container-images. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-12.
  • Accelerate Machine Learning Local Development and Test Workflows with Nvidia Docker
    6 projects | dev.to | 12 Feb 2023
    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 /
  • Run Playwright tests with hardware acceleration on a GPU-enabled EC2 instance with Docker support
    1 project | dev.to | 4 Aug 2022
    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.
  • CUDA 11.7 released with Ubuntu 22.04 support
    1 project | /r/nvidia | 16 May 2022
    Looking forward to the CUDA containers getting released!
  • How to build ZED 2i Camera x ROS2 Foxy x Nvidia Jetson x Ubuntu 18.04 via Docker
    7 projects | dev.to | 15 Sep 2021
    # 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
  • Running Nvidia drivers in Clear Linux or Flatcar?
    5 projects | /r/homelab | 30 Aug 2021
    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.
  • Is it possible to install Nvidia drivers?
    3 projects | /r/virtualbox | 11 Aug 2021
    To add CUDA I plan on adding the stuff from this Docker script.
  • Can you add CUDA to a docker container?
    3 projects | /r/docker | 10 Aug 2021
    You can use the cuda dockerfile as reference: https://gitlab.com/nvidia/container-images/cuda/-/blob/master/Dockerfile
  • KDE Development with Podman
    3 projects | dev.to | 10 Aug 2021
    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.
  • Tensorflow build error
    1 project | /r/tensorflow | 8 Feb 2021
    https://gitlab.com/nvidia/container-images/cuda/-/issues/109#note_503061879

What are some alternatives?

When comparing jetson-containers and container-images you can also consider the following projects:

docker-images - Official source of container configurations, images, and examples for Oracle products and projects

nvidia-docker - Build and run Docker containers leveraging NVIDIA GPUs

zed-ros2-wrapper - ROS 2 wrapper for the ZED SDK

zed-docker - Docker images for the ZED SDK

onnxruntime - ONNX Runtime: cross-platform, high performance ML inferencing and training accelerator

jetson-containers - Machine Learning Containers for NVIDIA Jetson and JetPack-L4T

AiDungeon2-Docker-ROCm - Runs an AIDungeon2 fork in Docker on AMD ROCm hardware.

tensorflow-on-arm - TensorFlow for Arm

HR-VITON - Official PyTorch implementation for the paper High-Resolution Virtual Try-On with Misalignment and Occlusion-Handled Conditions (ECCV 2022).

coreos-assembler - Tooling container to assemble CoreOS-like systems