Config reference: docker
-
Enterprise tuning surface
Defaults + constraints are rendered directly from Pydantic.
-
Env keys when available
Many fields have an env-style alias (from
TriBridConfig.to_flat_dict()). -
Tooltip-level guidance
If a matching glossary entry exists, you’ll see deeper tuning notes.
Config reference Config API & workflow Glossary
Total parameters: 11
Group index
(root)
(root)
| JSON key | Env key(s) | Type | Default | Constraints | Summary |
|---|---|---|---|---|---|
docker.dev_backend_port | DEV_BACKEND_PORT | int | 8012 | ≥ 1024, ≤ 65535 | Port for dev backend (Uvicorn) |
docker.dev_frontend_port | DEV_FRONTEND_PORT | int | 5173 | ≥ 1024, ≤ 65535 | Port for dev frontend (Vite) |
docker.dev_stack_restart_timeout | DEV_STACK_RESTART_TIMEOUT | int | 30 | ≥ 5, ≤ 120 | Timeout for dev stack restart operations (seconds) |
docker.docker_container_action_timeout | DOCKER_CONTAINER_ACTION_TIMEOUT | int | 30 | ≥ 5, ≤ 120 | Timeout for Docker container actions (start/stop/restart) |
docker.docker_container_list_timeout | DOCKER_CONTAINER_LIST_TIMEOUT | int | 10 | ≥ 1, ≤ 60 | Timeout for Docker container list (seconds) |
docker.docker_host | DOCKER_HOST | str | "" | — | Docker socket URL (e.g., unix:///var/run/docker.sock). Leave empty for auto-detection. |
docker.docker_infra_down_timeout | DOCKER_INFRA_DOWN_TIMEOUT | int | 30 | ≥ 10, ≤ 120 | Timeout for Docker infrastructure down command (seconds) |
docker.docker_infra_up_timeout | DOCKER_INFRA_UP_TIMEOUT | int | 60 | ≥ 30, ≤ 300 | Timeout for Docker infrastructure up command (seconds) |
docker.docker_logs_tail | DOCKER_LOGS_TAIL | int | 100 | ≥ 10, ≤ 1000 | Default number of log lines to tail from containers |
docker.docker_logs_timestamps | DOCKER_LOGS_TIMESTAMPS | int | 1 | ≥ 0, ≤ 1 | Include timestamps in Docker logs (1=yes, 0=no) |
docker.docker_status_timeout | DOCKER_STATUS_TIMEOUT | int | 5 | ≥ 1, ≤ 30 | Timeout for Docker status check (seconds) |
Details (glossary)
docker.docker_container_action_timeout (DOCKER_CONTAINER_ACTION_TIMEOUT) — Container Action Timeout
Category: infrastructure
Maximum wait time for start, stop, or restart operations before the control layer marks the action as timed out. This setting protects UI/API responsiveness when containers hang during bootstrap, health checks, or shutdown hooks. If set too low, normal slow starts appear as failures; if set too high, real faults surface too late and block automation. Choose a value slightly above observed p95 action latency for your heaviest service profile and revisit after infrastructure changes.
Badges: - Timeout control
Links: - Docker startup performance study (arXiv 2026) - docker container start - docker container stop - docker container wait
docker.docker_container_list_timeout (DOCKER_CONTAINER_LIST_TIMEOUT) — Container List Timeout
Category: infrastructure
Upper bound for how long the system waits when requesting container listings from the Docker API. This mainly protects control-plane responsiveness in environments with many containers, remote contexts, or overloaded Docker daemons. Higher values reduce false timeout errors during heavy load, while lower values fail fast and keep UIs responsive when the daemon is unhealthy. Tune it from observed list latency, not guesswork, and monitor for growth as your service count increases.
Badges: - API latency
Links: - CrossTrace distributed tracing for microservices (arXiv 2025) - docker container ls - docker ps - Docker contexts
docker.docker_infra_down_timeout (DOCKER_INFRA_DOWN_TIMEOUT) — Infrastructure Down Timeout
Category: infrastructure
Controls how long the orchestrator waits for compose shutdown to complete before treating stop as failed. In RAG stacks this protects stateful services such as Postgres and vector stores, which need time to flush write-ahead logs and close files cleanly. If set too low, forced termination can leave partial writes, slower recovery, or integrity checks on restart; if set too high, rollback and local iteration become sluggish. Tune this from measured shutdown duration under heavy ingest and keep headroom for worst-case disk latency.
Badges: - Infrastructure shutdown
Links: - Docker Compose down - Compose stop_grace_period - Docker daemon reference - Decomposing Docker Container Startup Performance (2026)
docker.docker_infra_up_timeout (DOCKER_INFRA_UP_TIMEOUT) — Infrastructure Up Timeout
Category: infrastructure
Defines the maximum wait for infrastructure startup readiness. During first boot or after image updates, pulls, migrations, and service warm-up can dominate startup time in a RAG environment. If the timeout is too short, healthy services may be marked failed before they pass health checks; if too long, real boot failures surface late and slow feedback loops. Set this from observed cold-start timings and revisit it when adding heavy dependencies such as observability or graph services.
Badges: - Infrastructure startup
Links: - Docker Compose up - Compose healthcheck - Docker daemon reference - Decomposing Docker Container Startup Performance (2026)
docker.docker_logs_tail (DOCKER_LOGS_TAIL) — Log Lines to Tail
Category: infrastructure
Sets how many trailing log lines are fetched per container when debugging retrieval workflows. Smaller tails keep UI and CLI feedback fast for routine checks, while larger tails help reconstruct multi-step failures across chunking, embedding, indexing, and query handling. Extremely large tails increase I/O and can bury the newest signal in historical noise. Use a conservative default and temporarily raise the value during incident analysis.
Badges: - Log visibility
Links: - docker container logs - Docker logging drivers - Grafana Loki docs - Sharpening Kubernetes Audit Logs with Context Awareness (2025)
docker.docker_logs_timestamps (DOCKER_LOGS_TIMESTAMPS) — Include Log Timestamps
Category: infrastructure
Adds timestamps to container output so events can be correlated across services in a single RAG request path. This is critical when tracing latency between ingestion, embedding calls, vector writes, and generation. Without timestamps, parallel service events are easy to misorder and root-cause analysis takes longer. Keep timestamps enabled for shared and production-like environments, and normalize timezone handling in downstream log tools.
Badges: - Correlation ready
Links: - docker container logs - Docker logging drivers - Grafana Loki docs - Sharpening Kubernetes Audit Logs with Context Awareness (2025)
docker.docker_status_timeout (DOCKER_STATUS_TIMEOUT) — Docker Status Timeout
Category: infrastructure
Sets the maximum time allowed for each Docker status probe. Low values surface daemon failures quickly but can create false negatives under CPU, disk, or socket contention; high values reduce noise but delay detection of real outages. In retrieval pipelines this directly affects whether preflight checks pass before ingestion and evaluation tasks begin. Choose a value slightly above observed probe latency at peak local load.
Badges: - Probe tuning
Links: - docker system info - Compose healthcheck - Docker Compose up - Decomposing Docker Container Startup Performance (2026)