_{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+)}

To start the container, you can use jetson-containers run and autotag, or manually put together a docker run command:

bash
# automatically pull or build a compatible container image
jetson-containers run $(autotag cuda)

# or explicitly specify one of the container images above
jetson-containers run dustynv/cuda:12.2-samples-r36.2.0

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host dustynv/cuda:12.2-samples-r36.2.0

^{jetson-containers run 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:

bash
jetson-containers run -v /path/on/host:/path/in/container $(autotag cuda)

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

bash
jetson-containers run $(autotag cuda) my_app --abc xyz

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