Closed TyPilot closed 1 year ago
This does happen on large containers right now, as the time between the stop command and the status check is currently hardcoded to five seconds. I will fix that soon, probably with a small subroutine to give it several tries.
Fixed in latest commit #7
Awesome! I'm assuming I just restart the bot for the update to take affect? Thanks!
Priority: low Impact: UI/user communication Issue: When running the command
/docker dockername:CONTAINER_NAME command:stop
, the request returns that it was not able to stop the server. However, when checking/list
, it has indeed stopped.