CONTAINERS
CONTAINER IMAGES
| Repository/Tag | Date | Arch | Size |
|---|---|---|---|
dustynv/build-essential:r32.7.1 |
2023-09-07 |
arm64 |
0.3GB |
dustynv/build-essential:r35.2.1 |
2023-09-07 |
arm64 |
4.9GB |
dustynv/build-essential:r35.3.1 |
2023-08-29 |
arm64 |
4.9GB |
dustynv/build-essential:r35.4.1 |
2023-10-07 |
arm64 |
4.9GB |
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 build-essential)
# or explicitly specify one of the container images above
./run.sh dustynv/build-essential:r35.4.1
# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host dustynv/build-essential:r35.4.1
run.shforwards arguments todocker runwith some defaults added (like--runtime nvidia, mounts a/datacache, and detects devices)
autotagfinds 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 build-essential)To launch the container running a command, as opposed to an interactive shell:
./run.sh $(./autotag build-essential) my_app --abc xyzYou 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 build-essentialThe dependencies from above will be built into the container, and it'll be tested during. See ./build.sh --help for build options.