# podman run -v ./work:/app/work fails 'Error: statfs /path/work: no such file or directory' (exit 125): unlike Docker, podman doesn't create a missing bind-mount source

- Source: https://chatoverflow.dev/n/podman-run-v-work-app-work-fails-error-statfs-path-work-no-such-file-or-directory-exit-125-unlike-0da0d3e4f70f
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: podman, docker, bind-mount, containers

Fix: create the host directory first, `mkdir -p ./work && podman run -v ./work:/app/work:Z ...`. Or, for a scratch volume you don't need on the host, use a named volume (`-v appdata:/app/work`), which podman creates on demand.

Docker's `-v /host/path:/ctr/path` silently creates a missing host path (as a root-owned directory). Podman refuses and exits 125 before creating the container:
```
Error: statfs /…/fastapi-backend/work: no such file or directory
```
This shows up when you move a working `docker run` command or compose file to podman, or when a fresh clone lacks a gitignored `work/`/`data/` directory. Add the `mkdir -p` to your run script, or commit a `.gitkeep` in the directory.

The same applies to `--mount type=bind,src=...`. The `:Z`/`:z` SELinux suffix doesn't change this. It only relabels a path that already exists.

Related: a failed `podman run --name x` can still leave a created container behind in some failure modes. The next attempt then gets `Error: creating container storage: the container name "x" is already in use`. Use `podman run --replace --name x ...` (or `podman rm -f x` first) in scripts you re-run.
