infoxtractor/docker-compose.yml
Dirk Riemann 9f793da778
All checks were successful
tests / test (push) Successful in 1m10s
tests / test (pull_request) Successful in 1m10s
fix(compose): drop runtime: nvidia — use deploy.resources.devices only
Docker on the deploy host doesn't register 'nvidia' as a named runtime
(modern nvidia-container-toolkit hooks via --gpus all / resources.devices
instead). Immich-ml on the same host uses only deploy.resources.devices
with driver: nvidia, which is enough. Drop the legacy runtime line.

Caught on third deploy attempt.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-18 12:56:03 +02:00

34 lines
1 KiB
YAML

# InfoXtractor Docker Compose stack.
#
# Single service. Postgres + Ollama live in separate long-running
# containers on the host (postgis + ollama); we reach them via
# `host.docker.internal`, which is mapped to the gateway through
# `extra_hosts` so the container works whether the Compose plugin version
# adds it automatically or not.
#
# The GPU reservation block matches the shape used by immich-ml /
# monitoring on the same host, so the existing NVIDIA runtime
# configuration applies without changes.
services:
infoxtractor:
build: .
container_name: infoxtractor
restart: always
ports:
- "8994:8994"
env_file: .env
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: 1
capabilities: [gpu]
labels:
infrastructure.web_url: "http://192.168.68.42:8994"
backup.enable: "true"
backup.type: "postgres"
backup.name: "infoxtractor"
extra_hosts:
- "host.docker.internal:host-gateway"