torch3d

torch3d

CONTAINERS IMAGES RUN BUILD

CONTAINERS

pytorch3d:0.7.8
Requires	L4T ['==36.*']
Dependencies	build-essential pip_cache:cu126 cuda:12.6 python cmake cudnn numpy onnx pytorch:2.8 torchvision torchaudio
Dockerfile	Dockerfile

pytorch3d:0.7.9
Aliases	pytorch3d
Requires	L4T ['>=36']
Dependencies	build-essential pip_cache:cu126 cuda:12.6 python cmake cudnn numpy onnx pytorch:2.8 torchvision torchaudio
Dependants	3d_diffusion_policy 3dgrut:2.0.0 4k4d:0.0.0 comfyui diffusion_policy easyvolcap:0.0.0 fast_gauss:1.0.0 isaac-gr00t l4t-diffusion pytorch:2.1-all pytorch:2.2-all pytorch:2.3-all pytorch:2.3.1-all pytorch:2.4-all pytorch:2.5-all pytorch:2.6-all pytorch:2.7-all pytorch:2.8-all self-forcing
Dockerfile	Dockerfile

RUN CONTAINER

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

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

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

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

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

jetson-containers run $(autotag torch3d) 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.

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:

jetson-containers build torch3d

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