#Thanks. I read this. I wish it was more

1 messages · Page 1 of 1 (latest)

fading sundial
#

I think the best analogy to think of is Docker in Docker. The engine runs in a container and its executing buildkit inside of that container. You're not going to be able to run docker ps to inspect those, but if you were to enter into the engine and run ps you would see various services starting up and shutting down depending on what you're build looks like.

By default dagger CLI will

  1. Connect to local running Docker
  2. Spin up an engine container or reuse an existing one

You can also point it to a remote engine as shown here: https://docs.dagger.io/manuals/administrator/472258/custom-runner#connection-interface

Use a Custom Runner | Dagger

A runner is the "backend" of the Dagger Engine where containers are actually executed.