Open prologic opened 6 years ago
@prologic I believe the original motivation of using DinD is explained here. It looks like there is a way to run directly, but the default being DinD is definitely a talking point.
Yeah I can't think of any good reasons why DinD should be the default here or why you'd want functions to run inside Docker inside Docker.
It also means if you want to scale those functions you'd have to scale the DinD environment too Uggh
James Mills / prologic
E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au
On Thu, Sep 7, 2017 at 9:12 AM, Dylan Stamat notifications@github.com wrote:
@prologic https://github.com/prologic I believe the original motivation of using DinD is explained here https://github.com/iron-io/functions/blob/3c4261ae37accf6c51a6aee6b216f58c84621d6c/docs/operating/options.md. It looks like there is a way to run directly, but the default being DinD is definitely a talking point.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iron-io/functions/issues/632#issuecomment-327846545, or mute the thread https://github.com/notifications/unsubscribe-auth/ABOv-v-t9f9t_q0gc5_8WO_RjRe1nEYiks5sgBSIgaJpZM4O0cvQ .
I'm not having a lot of success getting a e2e simple example going :/
Noticed while poking around that DinD is being used as a way to run the functions?
Why? This seems like a poor design choice to me -- not the least which the Docker engine being spawned doesn't seem to be running successfully without crashing.