#testing dagger in dagger
1 messages · Page 1 of 1 (latest)
You don't need docker at all for this. Dagger supports nesting as a native feature
Oooh!
Just set the ExperimentalPrivilegedNesting option in WithExec, and that command can magically make dagger API calls in the correct (nested) context
This works at arbitrary depth, too. So you can have dagger-in-dagger-in-dagger, etc
That's pretty awesome, definitely solves the horrid dind problems I've faced in the past. At least at the dagger level 😉
yeah, one benefit of having built Docker is that we know exactly where the most painful problems are, and we get to go back in time and fix it early 🙂
here's an example Adrian https://twitter.com/solomonstre/status/1605766970816823296
Some of you will appreciate this. It sure blew my mind..
When @dagger_io runs a container, that container now has full Dagger API access. It can then run more containers, and so on AT ARBITRARY DEPTH.
Infinite Dagger in Dagger 🤯
See for yourself: https://t.co/6paam5R0Gu
Lmao, this is awesome. Thank you for the example, I got it working for my node tests and it works flawlessly on the first try! 🤯
we test dagger-in-dagger in our CI as a sanity check for other tests we run on top of it, here's a couple more examples
@royal juniper That's awesome, love the gha in cue. The gha yaml is so impossible.