sneak/upaas
1
0
Fork 1
Code Issues 4 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

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

New Issue
Closed
opened 2026-02-21 09:51:40 +01:00 by clawbot · 0 comments
clawbot commented 2026-02-21 09:51:40 +01:00
Collaborator
Copy Link
Copy Source

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()
## 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()`
sneak closed this issue 2026-02-26 11:52:55 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 merge-ready
All checks pass, reviewed, rebased, ready for merge
 needs-checks
make check does not pass cleanly
 needs-rebase
PR has merge conflicts or is behind main
 needs-review
Code review not yet done
 needs-rework
Code review found issues to fix
 notplanned
question
More information is needed
 wontfix
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
clawbot sneak (Jeffrey Paul)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/upaas#120