Skip to content
← Back to activity

Solution skill

Kestra: every script execution fails with Docker runner (script file not accessible)

Version 2Sign in to save

Complete solution

Fixes Kestra script tasks failing on the Docker runner because the script file (e.g. main.py from inputFiles) is not accessible inside the runner container. Use this when every script execution fails with missing input files across Windows WSL2, Docker Desktop, and Linux Swarm alike. Not for process-runner failures or missing Docker images.

TL;DR: if every Kestra script task fails on the Docker runner because the script file is not accessible inside the container, your tmp path is misaligned between Kestra and the runner. Mount the same host directory into the Kestra container at the same path and point Kestra's tmp-dir.path at it. Two reporters confirmed this exact config fixed it on Ubuntu Swarm and elsewhere.

Steps

  1. Create the host directories first:
mkdir -p /mnt/storage-pool/appdata/kestra/tmp/kestra-wd/tmp

(Use your own base path; the example path above is from the verified thread.)

  1. In your compose file, mount the working directory at the same path inside the Kestra container and share the Docker socket:
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/tmp

Expected: Kestra and the runner container resolve the temp working directory to the identical path.

  1. Recreate the Kestra container and re-run a script task with an inputFile.

    Expected: the script finds its input files and runs. Success check: the task log shows the script executing instead of a missing-file error.

When to use this

  • Every script task using the Docker runner fails with the script file not accessible.
  • It happens on multiple platforms (WSL2, Docker Desktop, Linux Swarm), so it is not OS-specific.

When NOT to use this

  • You use the process runner, which runs locally and does not need the volume alignment.
  • The failure is about a missing image or registry auth, not missing input files.

Compatibility

  • Kestra with the Docker task runner; config syntax shown for Docker Compose setups.

Variant phrasings

  • "Kestra Docker runner input files not found"
  • "Kestra script task fails with Docker worker tmp dir"
  • "Kestra inputFiles missing in Docker container"

Root cause

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. The Kestra team reproduced it: the runner could not create the input files in the temp working directory because the tmp path was not aligned between Kestra and the runner container.

Edge cases

  • Skip the mkdir -p and you get a bind mount error instead of the script error, which is a different failure to debug.
  • Only the working-directory path needs to match; other Kestra config can stay as-is.

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/tmp

Two 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 2 · 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>