Skip to content

Files

Latest commit

996fd61 · Jan 29, 2024

History

History
This branch is 1482 commits behind dusty-nv/jetson-containers:master.

torch2trt

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 

torch2trt

CONTAINERS IMAGES RUN BUILD

CONTAINERS
torch2trt
   Builds torch2trt_jp51 torch2trt_jp46
   Requires L4T >=32.6
   Dependencies build-essential cuda cudnn python tensorrt numpy cmake onnx pytorch torchvision
   Dependants l4t-pytorch local_llm nanodb nanoowl nanosam
   Dockerfile Dockerfile
   Images dustynv/torch2trt:r32.7.1 (2023-12-14, 1.1GB)
dustynv/torch2trt:r35.2.1 (2023-12-14, 5.5GB)
dustynv/torch2trt:r35.3.1 (2023-08-29, 5.5GB)
dustynv/torch2trt:r35.4.1 (2023-12-05, 5.5GB)
CONTAINER IMAGES
Repository/Tag Date Arch Size
  dustynv/torch2trt:r32.7.1 2023-12-14 arm64 1.1GB
  dustynv/torch2trt:r35.2.1 2023-12-14 arm64 5.5GB
  dustynv/torch2trt:r35.3.1 2023-08-29 arm64 5.5GB
  dustynv/torch2trt:r35.4.1 2023-12-05 arm64 5.5GB

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 torch2trt)

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

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host dustynv/torch2trt: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 torch2trt)

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

./run.sh $(./autotag torch2trt) 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 torch2trt

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