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
If I start a program on the terminal, using docker run <img>, it may block the terminal. Then, if I press ^C it breaks out of that. However, if I first enter ^Z I will have suspended dumb-init and cannot use ^C anymore. That is not very useful, and maybe should be opted out from?
It would have made sense if we could send ^Z to the Docker command, which would send it inward and then pause the container, but it doesn't.
The text was updated successfully, but these errors were encountered:
Nice little utitility, and useful, thanks!
The lines
https://github.com/Yelp/dumb-init/blob/master/dumb-init.c#L120-L122
cause behaviour that seems problematic, yet they are hard-wired. I wonder why?
If I start a program on the terminal, using
docker run <img>
, it may block the terminal. Then, if I press^C
it breaks out of that. However, if I first enter^Z
I will have suspendeddumb-init
and cannot use^C
anymore. That is not very useful, and maybe should be opted out from?It would have made sense if we could send
^Z
to the Docker command, which would send it inward and thenpause
the container, but it doesn't.The text was updated successfully, but these errors were encountered: