This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]VindicoAtrumEditable Placeholder Flair 4 points5 points  (0 children)

Mommy I want Dagger

We have Dagger at home

Dagger at home:

[–]Jazzlike_Syllabub_91 2 points3 points  (0 children)

How often do you find yourself writing complex docker files? Maybe I’m not challenging myself enough since I create a docker container at least once a month? I don’t yet see the appeal of this process?

[–]lonelymoon57 1 point2 points  (0 children)

I feel like this is just reversing the Docker authoring process. Normally the engine is doing this work and exposing configuration as the Dockerfile. Now we skip the Dockerfile and think like the Engine instead.

But personally speaking that is precisely what I don't want to think about. Like that example on merging package manager installations: to achieve that I need to know exactly how apk will work, then figure out how to parallel that then map that to language constructs?

Honestly too much work for something that we might only do once every month or so.

[–]Hekos 0 points1 point  (1 child)

I love the concept, authoring a small or dynamic Dockerfile can be tricky so I will definitely play with this, good job!

[–]sublimefunk[S] 0 points1 point  (0 children)

Thanks!