Skip to content

Latest commit

 

History

History
 
 

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

h5py

CONTAINERS IMAGES RUN BUILD

CONTAINERS
h5py
   Requires L4T ['>=32.6']
   Dependencies build-essential pip_cache python
   Dependants crossformer diffusion_policy fruitnerf:1.0 isaaclab:2.2.0 isaacsim:5.0.0 l4t-ml l4t-tensorflow:tf1 l4t-tensorflow:tf2 lerobot mimicgen nano_llm:24.4 nano_llm:24.4-foxy nano_llm:24.4-galactic nano_llm:24.4-humble nano_llm:24.4-iron nano_llm:24.4.1 nano_llm:24.4.1-foxy nano_llm:24.4.1-galactic nano_llm:24.4.1-humble nano_llm:24.4.1-iron nano_llm:24.5 nano_llm:24.5-foxy nano_llm:24.5-galactic nano_llm:24.5-humble nano_llm:24.5-iron nano_llm:24.5.1 nano_llm:24.5.1-foxy nano_llm:24.5.1-galactic nano_llm:24.5.1-humble nano_llm:24.5.1-iron nano_llm:24.6 nano_llm:24.6-foxy nano_llm:24.6-galactic nano_llm:24.6-humble nano_llm:24.6-iron nano_llm:24.7 nano_llm:24.7-foxy nano_llm:24.7-galactic nano_llm:24.7-humble nano_llm:24.7-iron nano_llm:main nano_llm:main-foxy nano_llm:main-galactic nano_llm:main-humble nano_llm:main-iron nerfstudio:1.1.7 octo openpi openvla openvla:mimicgen robomimic tensorflow2:2.16.1 tensorflow2:2.18.0 tensorflow2:2.19.0 tensorflow2:2.20.0 tensorflow2:2.21.0 tensorflow_graphics:2.18.0 tensorflow_graphics:2.19.0 tensorflow_graphics:2.20.0 tensorflow_text:2.18.0 tensorflow_text:2.19.0 tensorflow_text:2.20.0
   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 h5py)

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

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

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

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