Bug: root .env AUTOBOT_TLS_CERT_DIR breaks Docker compose validation

[mrveiss]

Problem

The root .env file sets AUTOBOT_TLS_CERT_DIR=infrastructure/shared/certs for fleet deployment. In Docker context, this path doesn't exist, causing:

service "autobot-frontend" refers to undefined volume infrastructure/shared/certs: invalid compose project

The docker-compose.yml defaults to ./docker/certs but the .env override takes precedence.

Fix Options

1. Use docker/.env.docker for Docker-specific overrides (already exists but doesn't set this var)
2. Add AUTOBOT_TLS_CERT_DIR=./docker/certs to docker/.env.docker
3. Document that Docker startup requires AUTOBOT_TLS_CERT_DIR=./docker/certs env override

Discovered During

Docker deployment session, 2026-03-26.

Impact

High — Docker compose cannot validate or start without manual env override.

[mrveiss]

Workaround: pass AUTOBOT_TLS_CERT_DIR=./docker/certs when running Docker compose. Root cause: the shared .env file sets this to the fleet path (infrastructure/shared/certs) which doesn't exist in Docker context. This issue remains open — needs a proper solution (e.g., Docker-specific env file at compose level, or conditional logic).

[mrveiss]

Fixed in PR #2476 (merged). Added Docker TLS cert path override to docker/.env.docker.

[mrveiss]

Fixed in commit 8940f31 — hardcoded ./docker/certs for the cert volume mount (always correct in Docker context) and renamed nginx config var to AUTOBOT_DOCKER_NGINX_CONF to avoid collision with fleet .env vars. Docker compose now validates without any env overrides.