# Docker Compose Volume Mount "bind source path does not exist" in CI

> Fix Docker Compose "error mounting ... bind source path does not exist" in CI - a relative bind-mount host path that is missing on the runner, or a wrong volume short-syntax.

Source: https://latchkey.dev/learn/docker/docker-compose-volume-mount-source-path-not-exist  
Updated: 2026-06-25

A Compose bind mount pointed at a host path that does not exist on the runner. Compose (unlike Docker’s implicit create) refuses to mount a missing bind source, so the container fails to start.

## Diagnose it: read the resolved config, not the file you wrote

Compose merges override files, interpolates variables, and applies defaults before it does anything. Most Compose failures in CI are visible in the resolved configuration and invisible in the source file, because the value you are debugging came from an unset variable that quietly became an empty string.

```Terminal
# the fully merged, interpolated configuration Compose will actually run
docker compose config

# fail loudly on unset variables instead of silently interpolating empty
docker compose --env-file .env config --quiet || echo "invalid"

# which override files were picked up
docker compose config --services
```

> An unset variable interpolates to an empty string rather than erroring, so `image: myapp:${TAG}` becomes `myapp:` and fails later with a confusing reference error. `docker compose config` shows you the empty value directly.

## Bind mounts behave differently on a runner

- A relative bind source is resolved against the compose file location, not the working directory of the shell that invoked it.
- The host path must exist before `up`. Compose creates missing directories for named volumes but not for bind mounts, and the failure surfaces as a mount error rather than a missing-path error.
- On a CI runner the workspace path differs from your machine, so any absolute host path in a compose file is a portability bug waiting for its first CI run.
- Prefer named volumes for anything that does not genuinely need to be read from the host. They remove the whole class of problem.

## FAQ

### What causes Docker Compose volume mount "bind source path does not exist" in CI?

There are 3 common causes: the relative host path is absent on the runner, wrong volume short-syntax interpreted as a bind, and path relative to the wrong working directory. A ./data:/var/lib/data bind expects ./data to exist relative to the compose file.

### How do I fix Docker Compose volume mount "bind source path does not exist" in CI?

There are 2 fixes depending on which cause you have: create the bind source before composing up and use a named volume when no host path is needed. Work through them in order, since the first is the most common.

### What does Docker Compose volume mount "bind source path does not exist" in CI actually mean?

A docker compose up fails to start a service with error while creating mount source path / bind source path does not exist: <path>.

### How do I stop Docker Compose volume mount "bind source path does not exist" in CI happening again?

Create bind-mount host directories in the job before compose up. The prevention section lists 3 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt