Dagger
CertifiedTasks that run Dagger pipelines, commands, and scripts from Kestra.
Run Dagger CLI pipelines from Kestra using Commands for one or more inline pipeline expressions or Script for an inline multi-step script. Both run through a script task runner (Process or Docker) and auto-install a pinned, checksum-verified Dagger CLI when it is not already available.
Dagger
Tasks that run Dagger pipelines, commands, and scripts from Kestra.
Run Dagger CLI pipelines from Kestra using Commands for one or more inline pipeline expressions or Script for an inline multi-step script. Both run through a script task runner (Process or Docker) and auto-install a pinned, checksum-verified Dagger CLI when it is not already available.
tasks
How to use the Dagger plugin
Run Dagger pipelines and inline scripts from Kestra flows using the Dagger CLI.
Tasks
Commands runs one or more Dagger pipeline expressions — set commands (required list; each entry is passed individually to dagger shell -c). Script runs an inline Dagger script — set script (required; written to a temp file and piped to dagger shell via stdin). Use Script for multi-step pipelines authored inline; use Commands for discrete pipeline calls.
Both tasks default containerImage to curlimages/curl: latest. When the Dagger CLI is not already on PATH, a pinned version is downloaded and checksum-verified at runtime — this needs curl, tar, and sha256sum in the image, which the default image provides, so it works without modification. Override containerImage to use a custom base image, for example one with the Dagger CLI already installed. When using the Process task runner, containerImage is ignored and Dagger must be available on the host.
Setup and environment
Use beforeCommands for setup steps that run before the pipeline, and env to pass environment variables. Store credentials such as registry tokens in secrets and reference them from env.
Apply plugin defaults to share runner configuration across tasks.
