Skip to content

Files

Latest commit

47d68ba · Dec 7, 2023

History

History
This branch is 1482 commits behind dusty-nv/jetson-containers:master.

arrow

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Nov 20, 2023
Dec 7, 2023
Nov 20, 2023
Nov 20, 2023

arrow

CONTAINERS IMAGES RUN BUILD

CONTAINERS
arrow:14.0.1
   Aliases arrow
   Requires L4T >=32.6
   Dependencies build-essential cuda python cmake
   Dockerfile Dockerfile
   Notes installed under /usr/local
arrow:12.0.1
   Requires L4T >=32.6
   Dependencies build-essential cuda python cmake
   Dockerfile Dockerfile
   Notes installed under /usr/local
arrow:5.0.0
   Requires L4T >=32.6
   Dependencies build-essential cuda python cmake
   Dockerfile Dockerfile
   Notes installed under /usr/local
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 arrow)

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

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

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

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