Immutable solution version
Kestra: every script execution fails with Docker runner (script file not accessible)
Complete solution
Teaches the verified fix from a real kestra support thread: kestra: every script execution fails with Docker runner (script file not accessible)
What this fixes
Every script task using the Docker runner in Kestra failed: the script file (e.g. main.py from inputFiles) wasnt accessible inside the runner container. It happened on Windows with WSL2, on Docker Desktop, and on a Linux Docker Swarm setup, so it wasnt Windows-specific. The Kestra team reproduced it: the Docker runner couldnt create the input files in the temp working directory because the tmp path wasnt aligned between Kestra and the runner container.
The fix
The Docker runner mounts a shared volume for the working directory, so the temp path has to be identical on the Kestra side and the runner side. If you customize it, mount the same host directory into the Kestra container at the same path and tell Kestra to use it:
services:
app:
volumes:
- /mnt/storage-pool/appdata/kestra/tmp/kestra-wd:/mnt/storage-pool/appdata/kestra/tmp/kestra-wd
- /var/run/docker.sock:/var/run/docker.sock
environment:
KESTRA_CONFIGURATION: |
kestra:
tasks:
tmp-dir:
path: /mnt/storage-pool/appdata/kestra/tmp/kestra-wd/tmpTwo reporters confirmed this config fixed it ("This works on ubuntu/swarm", "with tmp path like in your example it works"). Create the host directories beforehand with mkdir -p, or youll get a bind mount error instead.
Source: https://github.com/kestra-io/kestra/issues/3590
Why it happens
The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.
Source
https://github.com/kestra-io/kestra/issues/3590
Evidence
Asked in the thread (https://vectle.com/threads/thr_I8KpgO7pHtrS15QmGlxpkw): Every script task using the Docker runner in Kestra failed: the script file (e.g. main.py from inputFiles) wasnt accessible inside the runner container. It happened on Windows with WSL2, on Docker Desktop, and on a Linux Docker Swarm setup, so it wasnt Windows-specific. The Kestra team reproduced it: the Docker runner couldnt create the input files in the temp working directory because the tmp path wasnt aligned between Kestra and the runner container. Verified resolution: The Docker runner mounts a shared volume for the working directory, so the temp path has to be identical on the Kestra side and the runner side. If you customize it, mount the same host directory into the Kestra container at the same path and tell Kestra to use it:
services:
app:
volumes:
- /mnt/storage-pool/appdata/kestra/tmp/kestra-wd:/mnt/storage-pool/appdata/kestra/tmp/kestra-wd
- /var/run/docker.sock:/var/run/docker.sock
environment:
KESTRA_CONFIGURATION: |
kestra:
tasks:
tmp-dir:
path: /mnt/storage-pool/appdata/kestra/tmp/kestra-wd/tmpTwo reporters confirmed this config fixed it ("This works on ubuntu/swarm", "with tmp path like in your example it works"). Create the host directories beforehand with mkdir -p, or youll get a bind mount error instead.
Source: https://github.com/kestra-io/kestra/issues/3590
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_GTf8T-UoBd1bCDmxUvuoRQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Kestra: every script execution fails with Docker runner (script file not accessible) <span>— Vectle</span></a>