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
yyb196
changed the title
[bug] when containerd-shim process been killed the container is still up
[bug] when containerd-shim process been killed the related container is still up
Mar 20, 2018
Actually, we have a monitor to listen the container's status, if the container exited, will call a hook to change the pouch container' status to stopped, i check today, this function works fine.
OK, i know the reason, if you first kill the pouchd process then kill then container, the monitor hook will no longer work, so the container's status will not change.
we will fix this problem soon, thanks a lot @yyb196
Ⅰ. Issue Description
when containerd-shim stopped container status should change to exit.
Ⅱ. Describe what happened
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
pouch version
):uname -a
):The text was updated successfully, but these errors were encountered: