Ollama

​

Towbar manifest

id: ollama
name: Ollama
buildServer: null
deployment:
  type: image
  image: ollama/ollama@sha256:8262851b2846b87c649eddf3e76beb270c52f4d1bc94559f47efde16b0841551
container:
  port: 11434
  resources:
    cpus: 4
    memory: 8g
  network: application
  networkAlias: ollama
  volumes:
    - name: ollama
      mountPath: /root/.ollama
      initialData: image
environments:
  production:
    server: 192.0.2.10
rollout:
  type: recreate
  maintenanceMode: true
  reason: Persistent application data uses a single writer

​

Configure

1. Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP. Commit the manifests, then sync the repository and inspect the resolved configuration.
2. Keep the Service’s named volumes attached across deployments. Towbar’s Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
3. This manifest has no public domain. Use a trusted connection to the server for the first check. Add a public route only after configuring the product’s authentication or an access gateway.
4. Deploy the Service, then perform the checks below before enabling auto-deploy.

​

Verify