Skip to main content
RamaLama images can be used like any other containerized workload. While not exhaustive we’ve provided two strategies you can leverage when deploying to kubernetes.
Although model images which package both the runtime and the model into a single image are available, we generally advise mounting models as volumes onto a runtime image when deploying to production. This keeps runtime and model lifecycles independent and reduces image size.

OCI Image Volume (Kubernetes 1.33+)

As of Kubernetes 1.33 image volumes have officially been promoted into beta. With this feature, you’re now able to mount a container image as a read‑only volume. For many models we provide both raw OCI artifacts tagged by their file type (e.g. :gguf) and OCI images with the model file mounted under the /models tagged as :gguf-image.
Requires Kubernetes 1.33+ with OCI image volume support enabled in your cluster. GPU prerequisites apply to the GPU example below: NVIDIA drivers on nodes and the NVIDIA Device Plugin.

InitContainer (ORAS into emptyDir)

Use an initContainer to pull the model ORAS artifact (:gguf) into an emptyDir mounted at /models before the runtime starts. This strategy works on any currently supported version of Kubernetes without special volume types.

Operational Tips

  • Pin a specific RamaLama image tag for reproducible rollouts.
  • For other accelerators (ROCm, Intel GPU, etc.), browse tags at registry.ramalama.com and pull from rlcr.io/ramalama/*, then apply the appropriate device resources.
  • For persistence across pod restarts, replace emptyDir with a PVC and write to it from the initContainer once; subsequent restarts can mount the pre‑seeded PVC read‑only.