I'm really interested in dagger. It looks like the solution to a significant set of challenges I'm facing at work regarding dev env/build parity. We have our build pretty stable but small differences in environment between the build servers and dev environments are starting to cause some issues. Dagger feels like it might help standardize things.
Right now we use TeamCity for our build environment, and one of the advantages that I have there is that I can have a build chain that runs different steps of the build in parallel across multiple agents. I'd love to continue using that capability, especially since some of our end-to-end tests are long-running and processor intensive. Right now it seems like dagger expects to be running on a "single host", so I'd be worried about cache coherence and coordination.
Am I right that if I moved in the direction of using Dagger then I have to have a single dagger engine and single docker host controlling the build? Am I even understanding the model correctly?