bitsandbytes

bitsandbytes

CONTAINERS IMAGES RUN BUILD

CONTAINERS

bitsandbytes:builder
Requires	L4T ['==35.*']
Dependencies	build-essential cuda cudnn python numpy cmake onnx pytorch:2.2 torchvision huggingface_hub rust transformers
Dockerfile	Dockerfile.builder
Notes	fork of https://github.com/TimDettmers/bitsandbytes for Jetson

bitsandbytes
Builds
Requires	L4T ['==35.*']
Dependencies	build-essential cuda cudnn python numpy cmake onnx pytorch:2.2 torchvision huggingface_hub rust transformers
Dependants	text-generation-inference
Dockerfile	Dockerfile
Images	dustynv/bitsandbytes:r35.2.1 (2023-12-15, 5.9GB) dustynv/bitsandbytes:r35.3.1 (2023-12-11, 6.0GB) dustynv/bitsandbytes:r35.4.1 (2023-12-14, 5.9GB)
Notes	fork of https://github.com/TimDettmers/bitsandbytes for Jetson

CONTAINER IMAGES

Repository/Tag	Date	Arch	Size
dustynv/bitsandbytes:r35.2.1	2023-12-15	arm64	5.9GB
dustynv/bitsandbytes:r35.3.1	2023-12-11	arm64	6.0GB
dustynv/bitsandbytes:r35.4.1	2023-12-14	arm64	5.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 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 bitsandbytes)

# or explicitly specify one of the container images above
jetson-containers run dustynv/bitsandbytes:r35.2.1

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

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

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

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