Files
Maestro/docker-compose.debug.yaml
T
Admin cda3091ad8 fix(containers): remap identity bind sources to host paths in dev
The dev maestro container's data root is /data/.dcntrlized
(XDG_DATA_HOME=/data), but bind-mount sources are resolved on the daemon's
host namespace — a nonexistent /data/.dcntrlized/... source made Docker
create empty directories, so the auth hub saw /dcntrlized/pki/tls.crt as a
directory and TLS setup failed. DCNTRLIZED_HOST_DATA_ROOT (compose-injected,
/home/franciscofadigas/.dcntrlized) is now substituted for the container-internal prefix when
building identity bind sources. hostBindSource leaves paths unchanged on host
installs.
2026-08-16 16:34:46 +01:00

33 lines
1.1 KiB
YAML

services:
maestro-engine:
image: maestro
container_name: maestro
ports:
- "8080:8080"
volumes:
- "/var/run/docker.sock:/var/run/docker.sock"
- "${XDG_DATA_HOME:-${HOME}}/.dcntrlized:/data/.dcntrlized"
- "${HOME}:/host-home:ro"
networks:
- dcntrlized_net
build:
context: .
dockerfile: Dockerfile.debug
environment:
- DCNTRLIZED_DEV=true
- XDG_DATA_HOME=/data
# Host path backing the data root, so Maestro's containerized start path
# can produce bind-mount sources the daemon resolves on the host
# namespace (identity injection for infra/peers).
- DCNTRLIZED_HOST_DATA_ROOT=${XDG_DATA_HOME:-${HOME}}/.dcntrlized
- DCNTRLIZED_GITEA_URL=${DCNTRLIZED_GITEA_URL:-http://192.168.122.183:3000}
- GITEA_REGISTRY_RO_TOKEN=${GITEA_REGISTRY_RO_TOKEN}
- GITEA_RW_PACKAGE_TOKEN=${GITEA_RW_PACKAGE_TOKEN}
- GITEA_ORG=${GITEA_ORG:-Dcntrlized}
- GITEA_USER=${GITEA_USER:-admin}
- GIT_TOKEN=${GIT_TOKEN}
- REGISTRY_USER=${REGISTRY_USER:-admin}
networks:
dcntrlized_net:
external: true