Skip to content

Latest commit

 

History

History
 
 

causalconv1d

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 
 
 

causalconv1d

CONTAINERS IMAGES RUN BUILD

CONTAINERS
causalconv1d:1.4.0
   Aliases causalconv1d
   Requires L4T ['>=34.1.0']
   Dependencies build-essential pip_cache:cu122 python ninja cuda:12.2 cudnn numpy cmake onnx pytorch:2.2 torchvision torchaudio
   Dependants cobra:0.0.1 dimba:1.0 mamba:2.2.2 mambavision:1.0 videomambasuite:1.0
   Dockerfile Dockerfile
   Notes https://github.com/state-spaces/mamba
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 causalconv1d)

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

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

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

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