NVIDIA SDK Manager Documentation
Docker Images - v1.9.2 - Last updated May 11, 2023

1. Docker Images

1.1. Download and Install

  1. Download and install the Docker engine for your system: Install Docker Engine @ Docker Documentation.

    For Linux users, it is recommended that you enable managing Docker as a non-root user, as described in Post-installation steps for Linux @ Docker Documentation.

  2. From the download page, locate sdkmanager-[version].[build#]-[base_OS]_docker.tar.gz, where [version] and [build] represent the current version number and build number of SDK Manager.

  3. Download the file to your host machine.

  4. From a terminal, load the Docker image:

    docker load -i ./sdkmanager-[version].[build#]-[base_OS]_docker.tar.gz 

    It is recommended that you tag the version as "latest" for ease of use:

    docker tag sdkmanager:[version].[build#] sdkmanager:latest 

2. Using the SDK Manager Docker Image

2.1. Guidelines

  • The image is built for using SDK Manager CLI mode only. Refer to Install with the Command Line for more information.

  • Flashing the target device requires full access to the USB port on the host machine.

  Note:  

Creating a DRIVE image for DRIVE Software 10.0 is not currently supported.   

2.2. Base Usage

The Docker image is designed to be executed directly from the host, without the need to open the terminal inside the docker itself. The sdkmanager executable is the entrypoint.

SDK Manager CLI arguments should be used directly when running a new container:

  • SDK Manager CLI

    sdkmanager --ver
  • SDK Manager CLI with Docker

    docker run -it --rm sdkmanager --ver

Refer to Install with the Command Line for more information.

3. Additional Considerations

  • By default, the initial container has a clean profile and local database. This needs to be taken into consideration as far as how to use the image and when to save the changes (commit) into a new image. This will depend on the usage plans for the container if there is a plan to re-use it after installation or start each time from a clean phase. Alter your plans according to whether you intend to have a different container for each SDK release or a unique one.

  • Flashing requires privileged access and mapping USB ports into the container:

    --privileged -v /dev/bus/usb:/dev/bus/usb/ -v /dev:/dev -v /media/$USER:/media/nvidia:slave
  • Depending on your local network's security settings, you may need to set access to your local network with --network host. This is primarily needed if you want to interact with Jetson devices via L4T USB Device mode.

  • The local user inside the Docker is nvidia with nvidia as the password. The home folder is /home/nvidia.
  • Examples for setting the container for flashing and re-use are as follows:

    • Initial install and flash; this example uses JetPack 4.4.1 and the Jetson Nano NX Devkit.

      docker run -it --privileged -v /dev/bus/usb:/dev/bus/usb/ -v /dev:/dev -v /media/$USER:/media/nvidia:slave
      --name JetPack_NX_Devkit --network host sdkmanager --cli install --logintype devzone --product Jetson --target P3668-0000 --targetos Linux --version 4.4.1 --select 'Jetson OS' --deselect 'Jetson SDK Components' --flash all --license accept --staylogin true --datacollection enable --exitonfinish
    • After install and flash, commit the container as a new image.

      docker commit JetPack_NX_Devkit jetpack_nx_devkit:4.4.1_flash
      docker container rm  JetPack_NX_Devkit 
    • Next, flash can be executed from the created image directly, without additional arguments. The container can then be removed after flash is complete.

      docker run -it --rm --privileged -v /dev/bus/usb:/dev/bus/usb/ jetpack_nx_devkit:4.4.1_flash 

4. Known Issues

  • When installing JetPack SDK using the SDK Manager Docker image, you should first install qemu-user-static and binfmt-support on your host machine, then run the following command on your host machine:

    sudo update-binfmts --enable

    Without these steps, you will get the following error during installation from the File System and OS component:

    'dpkg': Exec format error
  • When installing the DRIVE SDK using the SDK Manager Docker image, flashing the target may fail if ADB is running on the host machine. Make sure to stop the ADB before flashing, using the following command on your host machine:

    sudo killall adb

Previous | Next

  Previous Topics     Next Topics  

System Requirements    

Download and Install SDK Manager    

SDK Manager Settings    

Home    

 

Notices

Notice

THE INFORMATION IN THIS GUIDE AND ALL OTHER INFORMATION CONTAINED IN NVIDIA DOCUMENTATION REFERENCED IN THIS GUIDE IS PROVIDED “AS IS.” NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE INFORMATION FOR THE PRODUCT, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. Notwithstanding any damages that customer might incur for any reason whatsoever, NVIDIA’s aggregate and cumulative liability towards customer for the product described in this guide shall be limited in accordance with the NVIDIA terms and conditions of sale for the product.

THE NVIDIA PRODUCT DESCRIBED IN THIS GUIDE IS NOT FAULT TOLERANT AND IS NOT DESIGNED, MANUFACTURED OR INTENDED FOR USE IN CONNECTION WITH THE DESIGN, CONSTRUCTION, MAINTENANCE, AND/OR OPERATION OF ANY SYSTEM WHERE THE USE OR A FAILURE OF SUCH SYSTEM COULD RESULT IN A SITUATION THAT THREATENS THE SAFETY OF HUMAN LIFE OR SEVERE PHYSICAL HARM OR PROPERTY DAMAGE (INCLUDING, FOR EXAMPLE, USE IN CONNECTION WITH ANY NUCLEAR, AVIONICS, LIFE SUPPORT OR OTHER LIFE CRITICAL APPLICATION). NVIDIA EXPRESSLY DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR SUCH HIGH RISK USES. NVIDIA SHALL NOT BE LIABLE TO CUSTOMER OR ANY THIRD PARTY, IN WHOLE OR IN PART, FOR ANY CLAIMS OR DAMAGES ARISING FROM SUCH HIGH RISK USES.

NVIDIA makes no representation or warranty that the product described in this guide will be suitable for any specified use without further testing or modification. Testing of all parameters of each product is not necessarily performed by NVIDIA. It is customer’s sole responsibility to ensure the product is suitable and fit for the application planned by customer and to do the necessary testing for the application in order to avoid a default of the application or the product. Weaknesses in customer’s product designs may affect the quality and reliability of the NVIDIA product and may result in additional or different conditions and/or requirements beyond those contained in this guide. NVIDIA does not accept any liability related to any default, damage, costs or problem which may be based on or attributable to: (i) the use of the NVIDIA product in any manner that is contrary to this guide, or (ii) customer product designs.

Other than the right for customer to use the information in this guide with the product, no other license, either expressed or implied, is hereby granted by NVIDIA under this guide. Reproduction of information in this guide is permissible only if reproduction is approved by NVIDIA in writing, is reproduced without alteration, and is accompanied by all associated conditions, limitations, and notices.

Trademarks

NVIDIA, the NVIDIA logo, Bluefield-2, CLARA, NVIDIA CLARA AGX SDK, cuBLAS, CUDA, CUDA-GDB, CUDA-MEMCHECK, cuDNN, cuFFT, cuSPARSE, DIGITS, DGX, DGX-1, DGX Station, NVIDIA DOCA SDK, NVIDIA DRIVE, NVIDIA DRIVE AGX, NVIDIA DRIVE Software, NVIDIA DRIVE OS, NVIDIA Developer Zone (aka "DevZone"), NVIDIA DOCA SDK, NVIDIA Ethernet Switch, NVIDIA Ethernet Switch SDK, GRID, Jetson, NVIDIA Jetson Nano, NVIDIA Jetson AGX Xavier, NVIDIA Jetson TX2, NVIDIA Jetson TX2i, NVIDIA Jetson TX1, NVIDIA Jetson TK1, Kepler, NGX, NVIDIA GPU Cloud, Maxwell, Multimedia API, NCCL, NVIDIA Nsight Compute, NVIDIA Nsight Eclipse Edition, NVIDIA Nsight Graphics, NVIDIA Nsight Systems, NVLink, nvprof, Pascal, NVIDIA Rivermax SDK, NVIDIA SDK Manager, Tegra, TensorRT, Tesla, Visual Profiler, VisionWorks and Volta are trademarks and/or registered trademarks of NVIDIA Corporation in the United States and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.