CRITICAL: docker-compose.yml missing HOST_DATA_DIR — git clone fails in containerized deployment #120

New Issue

clawbot · 2026-02-21T09:51:40+01:00

clawbot commented

2026-02-21 09:51:40 +01:00

Bug

When running upaas via docker-compose up, git clone operations fail because Docker bind mounts use container-internal paths instead of host paths.

Root Cause

docker-compose.yml does not set UPAAS_HOST_DATA_DIR. The config defaults HostDataDir to DataDir when empty (config.go:113-115). Inside the container, DataDir = /var/lib/upaas. When CloneRepo is called, containerToHostPath() (deploy.go) returns the container path unchanged, so the git clone Docker container gets bind mounts pointing to /var/lib/upaas/builds/... — a path that exists inside the upaas container but not on the Docker host.

The git clone container runs on the host Docker daemon (via the mounted socket), so it cannot access these container-internal paths.

Impact

All deployments fail when upaas is run via docker-compose (the primary documented deployment method). Manual and webhook-triggered deploys both affected.

Fix

Either:

Add UPAAS_HOST_DATA_DIR to docker-compose.yml with the host-side path of the upaas-data volume, OR
Switch from a named volume to a bind mount so the host path is known and can be set automatically

Files

docker-compose.yml — missing env var
internal/config/config.go:113-115 — HostDataDir fallback
internal/service/deploy/deploy.go — containerToHostPath()

## Bug When running upaas via `docker-compose up`, git clone operations fail because Docker bind mounts use container-internal paths instead of host paths. ## Root Cause `docker-compose.yml` does not set `UPAAS_HOST_DATA_DIR`. The config defaults `HostDataDir` to `DataDir` when empty (`config.go:113-115`). Inside the container, `DataDir` = `/var/lib/upaas`. When `CloneRepo` is called, `containerToHostPath()` (`deploy.go`) returns the container path unchanged, so the git clone Docker container gets bind mounts pointing to `/var/lib/upaas/builds/...` — a path that exists inside the upaas container but **not** on the Docker host. The git clone container runs on the host Docker daemon (via the mounted socket), so it cannot access these container-internal paths. ## Impact All deployments fail when upaas is run via docker-compose (the primary documented deployment method). Manual and webhook-triggered deploys both affected. ## Fix Either: 1. Add `UPAAS_HOST_DATA_DIR` to `docker-compose.yml` with the host-side path of the upaas-data volume, OR 2. Switch from a named volume to a bind mount so the host path is known and can be set automatically ## Files - `docker-compose.yml` — missing env var - `internal/config/config.go:113-115` — HostDataDir fallback - `internal/service/deploy/deploy.go` — `containerToHostPath()`

clawbot referenced this issue from a commit

2026-02-21 09:57:36 +01:00

fix: use bind mount with HOST_DATA_DIR in docker-compose.yml (closes #120)

clawbot referenced a pull request that will close this issue

2026-02-21 09:57:56 +01:00

Fix 1.0 audit bugs (closes #120, closes #121, closes #122, closes #123, closes #124, closes #125) #126

clawbot referenced this issue

2026-02-21 16:45:34 +01:00

Fix 1.0 audit bugs (closes #120, closes #121, closes #122, closes #123, closes #124, closes #125) #126

clawbot referenced this issue

2026-02-21 20:45:37 +01:00

Fix 1.0 audit bugs (closes #120, closes #121, closes #122, closes #123, closes #124, closes #125) #126