cudf

cudf

CONTAINERS IMAGES RUN BUILD

CONTAINERS

cudf:23.10.03
Aliases	cudf
Builds
Requires	L4T >=36
Dependencies	build-essential cuda python cmake numpy cupy numba protobuf:apt
Dependants	cuml
Dockerfile	Dockerfile.jp5
Images	dustynv/cudf:23.10.03-r36.2.0 (2023-12-06, 5.2GB)
Notes	installed under /usr/local

cudf:21.10.02
Aliases	cudf
Requires	L4T ==35.*
Dependencies	build-essential cuda python cmake numpy cupy numba protobuf:apt
Dockerfile	Dockerfile.jp5
Notes	installed under /usr/local

CONTAINER IMAGES

Repository/Tag	Date	Arch	Size
dustynv/cudf:23.10.03-r36.2.0	2023-12-06	arm64	5.2GB
dustynv/cudf:r35.2.1	2023-09-07	arm64	6.4GB
dustynv/cudf:r35.3.1	2023-12-06	arm64	6.5GB
dustynv/cudf:r35.4.1	2023-10-07	arm64	6.4GB

_{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 cudf)

# or explicitly specify one of the container images above
./run.sh dustynv/cudf:23.10.03-r36.2.0

# or if using 'docker run' (specify image and mounts/ect)
sudo docker run --runtime nvidia -it --rm --network=host dustynv/cudf:23.10.03-r36.2.0

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

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

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

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