Cool, thanks for the clarification | Dagger | Page 1

Thanks!

Dagger is great at orchestrating containers and services that run in containers 🙂

Its not the best fit if you want to orchestrate native services though because its operations happen in a sandbox that does not know anything about the host.

With all that said, everything I just mentioned applies to running dagger modules. It is technically possible to run dagger as a regular code library instead dagger run in this mode you are creating your own dagger client that is more host aware.

The biggest downside to this approach is you lose the portability and cross-language abilities that dagger modules offer.

We're still working on moving this approach back into our docs (this is how dagger used to work before modules) but you could see an example of this here: https://archive.docs.dagger.io/0.9/sdk/go/959738/get-started

Those docs apply to the latest version of dagger as well.

Get Started with the Dagger Go SDK | Dagger

Introduction

#Cool, thanks for the clarification