Skip to content

Latest commit

 

History

History
89 lines (69 loc) · 4.8 KB

README.md

File metadata and controls

89 lines (69 loc) · 4.8 KB
Raw

ollama

CONTAINERS IMAGES RUN BUILD

Container Usage

Run the container as a daemon in the background docker run -d --gpus=all -v ollama:/root/.ollama -p 11434:11434 --name ollama dusty-nv/ollama

Start the Ollama front-end with your desired model (for example: mistral 7b) docker run -it --rm dusty-nv/ollama /bin/ollama run mistral

Memory Usage

Model Quantization Memory (MB)
TheBloke/Llama-2-7B-GGUF llama-2-7b.Q4_K_S.gguf 5,268
TheBloke/Llama-2-13B-GGUF llama-2-13b.Q4_K_S.gguf 8,609
TheBloke/LLaMA-30b-GGUF llama-30b.Q4_K_S.gguf 19,045
TheBloke/Llama-2-70B-GGUF llama-2-70b.Q4_K_S.gguf 37,655
CONTAINERS
ollama
   Requires L4T ['>=34.1.0']
   Dependencies build-essential cuda
   Dockerfile Dockerfile
   Images dustynv/ollama:r35.4.1 (2024-04-05, 5.4GB)
dustynv/ollama:r36.2.0 (2024-04-05, 3.9GB)
CONTAINER IMAGES
Repository/Tag Date Arch Size
  dustynv/ollama:r35.4.1 2024-04-05 arm64 5.4GB
  dustynv/ollama:r36.2.0 2024-04-05 arm64 3.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 ollama)

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

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

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

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

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