README.md

cmake_apt

CONTAINERS IMAGES RUN BUILD

CONTAINERS

cmake:apt
Builds
Requires	L4T ['>=32.6']
Dependencies	build-essential
Dependants	ros:melodic-desktop ros:melodic-ros-base ros:melodic-ros-core
Dockerfile	Dockerfile
Images	dustynv/cmake:apt-r32.7.1 (2023-09-07, 0.3GB) dustynv/cmake:apt-r35.2.1 (2023-08-29, 4.9GB) dustynv/cmake:apt-r35.3.1 (2023-09-07, 5.0GB) dustynv/cmake:apt-r35.4.1 (2023-10-07, 4.9GB)
Notes	upgrade cmake with apt

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

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host cmake_apt:35.2.1

^{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 cmake_apt)

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

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

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