Dagger

“I found the migration challenging because it's the heavy tool with its quirks.”

“I also see TypeSafe adopted Dagger which is awesome and hopefully inspires more confidence in the rest of the community.”

“I'm a happy user of Dagger. One use case I've found for it besides CI was building an eval sandbox”

“There's a very friendly and active community of CI/CD nerds, who will be happy to help.”

“increasingly I find myself using Dagger instead of Docker, in the context of my CI pipelines”

“both can invoke modules written in other languages from your language of choice”

“Docker Compose / K8S / VM / Dagger.io layers are close but can't quite always recurse flexibly”

“It's an open-source CI platform that decouples the runtime from the triggers.”

“I get a lot of the vscode benefits by presenting it as a virtual filesystem and terminal”

“My favorite features are powered by Dagger, sandbox with time travel, forking, jump into shell at any turn, diff between any points.”

“brings a number of capabilities like being able to drop into a shell in the same environment”

“They have an awesome renderer for OTEL spans (how they emit and view the steps).”

“at this point I'll take anything that does as much as possible at compile time”

“using a better tool to access containers (BuildKit), like Dagger, where you can track every step as a new container layer”

“supports dagger-in-dagger natively, with logical scoping, and without depth limit”

“Being able to run the exact same pipeline locally and in any CI environment is the most compelling feature of dagger.”

“Dagger's current caching implementation is very much built around there being a single long-lived node and doesn't scale out well”

“one of the main reasons we chose dagger as the underlying foundation of the platform in the first place”

“it makes this break-glass setup easier, by decoupling the CI logic from CI infrastructure”

“the whole point of using Dagger in this setup is to get tests caching out of the box”

“Dagger has been a godsend in helping me cope with the unending misery that is GitHub Actions.”

“The end-to-end integration allows us to do very magical things that traditional CI products cannot match.”

“Go look at what dagger provides over those technologies as a basis for advanced agent env capabilities”

“local-first (local execution should be a first-class citizen, with no exception)”

“I tried to convert one of our Actions workflows and that proved to be a PITA that I gave up on”

“Dagger is a pretty sweet piece of tech, so many uses for programmatic container layers”

“its module and function orchestration is a much more basic and first principle it embraces”

“It felt painful for me to abandon that investment, as I'm sure it did for many on your team, too.”

“It serves a place where a dockerfile is not enough, and CI workflows are too difficult to debug or reason about.”

“There's no reason you shouldn't be able to get precise cache invalidation in a large monorepo.”

“Works fine for us for glueing a bunch of CI steps together which would've been a pile of bash otherwise.”

“I recommend joining our Discord and asking our community directly about the pros and cons of using Dagger”

“it can’t export artifacts and import into other steps without breaking the cache”

“adds complexity to something I can already do with a Dockerfile and bash”

“Overall I like Dagger conceptually, but I wish they'd start focusing more on API stability and documentation”

“It does a pretty good job of caching and that does help speed up builds.”

“The base design is ok but there's things I'd do different today if I knew the build stuff would fade away for the LLM push.”

“local exec, sandboxing, determinism, and fine-grained (remote) caching for mere mortals”

“I've also looked at Dagger and been quite disappointed with it (and their terrible documentation).”

“I am now implementing environments for agents based on container layers and Dagger, which unlocks the ability to cheaply and reproducible clone what one agent was doing”