You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is wholeheartedly related to #2 but worth splitting out into its own issue - we must get to the bottom of why the combination of child processes aren't naturally exiting. Forcefully calling various .exit() methods (on children and parents) is leaving some docker containers running, and/or (not sure if it's a 1:1 mapping) several zombie node processes which seem to just chew up load.
See moby/moby#1320 for something which sounds vaguely similar.
Just need to step through layer step by step and hunt this down once and for all.
The text was updated successfully, but these errors were encountered:
This is wholeheartedly related to #2 but worth splitting out into its own issue - we must get to the bottom of why the combination of child processes aren't naturally exiting. Forcefully calling various .exit() methods (on children and parents) is leaving some docker containers running, and/or (not sure if it's a 1:1 mapping) several zombie node processes which seem to just chew up load.
See moby/moby#1320 for something which sounds vaguely similar.
Just need to step through layer step by step and hunt this down once and for all.
The text was updated successfully, but these errors were encountered: