Skip to content

Latest commit

 

History

History
80 lines (62 loc) · 4.97 KB

README.md

File metadata and controls

80 lines (62 loc) · 4.97 KB
Raw

tam

CONTAINERS IMAGES RUN BUILD

Track Anything from https://github.com/gaomingqi/Track-Anything

The tam container has a default run command to launch its web server app.

Use your web browser to access http://HOSTNAME:12212

CONTAINERS
tam
   Builds tam_jp60 tam_jp51
   Requires L4T >=34.1.0
   Dependencies build-essential cuda cudnn python tensorrt numpy cmake onnx pytorch:distributed torchvision onnxruntime opencv rust jupyterlab sam
   Dockerfile Dockerfile
   Images dustynv/tam:r35.2.1 (2023-12-12, 6.9GB)
dustynv/tam:r35.3.1 (2024-01-13, 7.0GB)
dustynv/tam:r35.4.1 (2023-11-04, 6.9GB)
dustynv/tam:r36.2.0 (2024-01-13, 8.6GB)
CONTAINER IMAGES
Repository/Tag Date Arch Size
  dustynv/tam:r35.2.1 2023-12-12 arm64 6.9GB
  dustynv/tam:r35.3.1 2024-01-13 arm64 7.0GB
  dustynv/tam:r35.4.1 2023-11-04 arm64 6.9GB
  dustynv/tam:r36.2.0 2024-01-13 arm64 8.6GB

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

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

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

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

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

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