act bind mount "no such file or directory" running Actions locally
act mounts host paths into the container (your repo, and any paths a step binds). Docker refuses the mount when the host path does not exist or is outside the directories Docker Desktop is allowed to share.
What this error means
act fails with "invalid mount config" or "bind source path does not exist" / "no such file or directory" when creating the job container.
act
docker: Error response from daemon: invalid mount config for type "bind":
bind source path does not exist: /Users/dev/project/artifactsCommon causes
The host path does not exist yet
A step binds a directory that a previous step was supposed to create, but it is not there when the mount happens.
The path is not shared with Docker Desktop
Docker Desktop only mounts paths under its configured file-sharing roots; a path outside them cannot be bound.
How to fix it
Create the path or add it to file sharing
- Ensure the host directory exists before the step that mounts it.
- In Docker Desktop Settings, Resources, File Sharing, add the parent directory.
- Re-run act after applying the sharing change.
Terminal
mkdir -p ./artifacts
act -j buildKeep mounted paths inside the repo
Bind paths within the working tree so they fall under an already-shared root.
How to prevent it
- Create directories before steps that bind-mount them.
- Add project roots to Docker Desktop file sharing.
- Prefer paths inside the repository for local mounts.
Related guides
act "actions/checkout" fails locally running Actions with actFix actions/checkout failures under act - by default act binds your working tree into the container, so a rea…
act "upload-artifact" fails without an artifact server locallyFix act upload-artifact / download-artifact failures - these actions need the GitHub artifact service, so act…
act "actions/cache" is a no-op running Actions locallyUnderstand act and actions/cache - the GitHub cache service does not exist locally, so actions/cache saves an…