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
During the SC bash tutorial, it's common to have only a shell open. The terminal doesn't appear to use the jupyter heartbeat or execution API. This causes containers that are only running the terminal to expire and be reclaimed by the system.
This happened to @matty-jones during a workshop. I watched a handful of containers expire, and Matty's was one of them. It clearly should still be alive.
There is no obvious solution, since we rely on the jupyter execution to keep our containers alive.
During the SC bash tutorial, it's common to have only a shell open. The terminal doesn't appear to use the jupyter heartbeat or execution API. This causes containers that are only running the terminal to expire and be reclaimed by the system.
This happened to @matty-jones during a workshop. I watched a handful of containers expire, and Matty's was one of them. It clearly should still be alive.
There is no obvious solution, since we rely on the jupyter execution to keep our containers alive.
/cc @mikemhenry
The text was updated successfully, but these errors were encountered: