Remote execution

Run any Dagger pipeline on a remote engine. Dagger securely streams local inputs and outputs as needed: files, secrets, network tunnels, terminal. Execution is fully sandboxed, so developers, agents and CI can safely pool compute and cache. Set --engine or DAGGER_ENGINE to SSH, TLS, Docker, Kubernetes. Or set to cloud for a managed engine with scale-out, distributed cache, access control and observability. Great for: faster CI, faster local builds, and running many agents without melting your machine.

The engine can run in different places:

• An engine that already runs: ssh://[USER@]HOST[:PORT], tls://HOST[:PORT], tcp://HOST:PORT (no authentication) or unix://PATH.
• Kubernetes: kube-pod://POD.
• A local container runtime: image://IMAGE starts an engine from an image, and container://NAME uses an engine container that already runs. Docker, Podman, Apple containers, Finch and nerdctl are supported.
• Dagger Cloud: cloud.

Run dagger help engine for the full list. The --cloud flag is deprecated: use --engine=cloud.

$ dagger check --engine=ssh://build-host