Skip to content

Latest commit

 

History

History
 
 

deepstream

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

deepstream

CONTAINERS IMAGES RUN BUILD

CONTAINERS
deepstream
   Builds deepstream_jp46 deepstream_jp51
   Requires L4T >=32.6
   Dependencies build-essential python cmake cuda cudnn numpy opencv gstreamer tritonserver
   Dockerfile Dockerfile
   Images dustynv/deepstream:r32.7.1 (2023-12-22, 2.3GB)
dustynv/deepstream:r35.2.1 (2023-12-22, 6.8GB)
dustynv/deepstream:r35.3.1 (2023-12-05, 6.8GB)
dustynv/deepstream:r35.4.1 (2023-12-06, 6.7GB)
   Notes https://docs.nvidia.com/metropolis/deepstream/dev-guide/text/DS_Quickstart.html
CONTAINER IMAGES
Repository/Tag Date Arch Size
  dustynv/deepstream:r32.7.1 2023-12-22 arm64 2.3GB
  dustynv/deepstream:r35.2.1 2023-12-22 arm64 6.8GB
  dustynv/deepstream:r35.3.1 2023-12-05 arm64 6.8GB
  dustynv/deepstream:r35.4.1 2023-12-06 arm64 6.7GB

Container images are compatible with other minor versions of JetPack/L4T:
    • L4T R32.7 containers can run on other versions of L4T R32.7 (JetPack 4.6+)
    • L4T R35.x containers can run on other versions of L4T R35.x (JetPack 5.1+)

RUN CONTAINER

To start the container, you can use the run.sh/autotag helpers or manually put together a docker run command:

# automatically pull or build a compatible container image
./run.sh $(./autotag deepstream)

# or explicitly specify one of the container images above
./run.sh dustynv/deepstream:r35.2.1

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host dustynv/deepstream:r35.2.1

run.sh forwards arguments to docker run with some defaults added (like --runtime nvidia, mounts a /data cache, and detects devices)
autotag finds a container image that's compatible with your version of JetPack/L4T - either locally, pulled from a registry, or by building it.

To mount your own directories into the container, use the -v or --volume flags:

./run.sh -v /path/on/host:/path/in/container $(./autotag deepstream)

To launch the container running a command, as opposed to an interactive shell:

./run.sh $(./autotag deepstream) my_app --abc xyz

You can pass any options to run.sh that you would to docker run, and it'll print out the full command that it constructs before executing it.

BUILD CONTAINER

If you use autotag as shown above, it'll ask to build the container for you if needed. To manually build it, first do the system setup, then run:

./build.sh deepstream

The dependencies from above will be built into the container, and it'll be tested during. See ./build.sh --help for build options.