CraziFuzzy Posted October 26, 2016 Share Posted October 26, 2016 What is the expected behavior when stopping a container from the Web UI? I am seeing the container being forced closed, and not stopping gracefully. docker stop from command-line sends sigterm and waits, but from the Web ui I am not seeing this behavior. I would really like to see the ui have a stop and a force stop, like the vm's have. Quote Link to comment
stuckless Posted October 26, 2016 Share Posted October 26, 2016 To add to this... is the web ui using 'docker kill' vs 'docker stop'... If so, I think the "STOP" in the WebUI should be using 'docker stop' to allow the container to gracefully shut down. Could the unRAID admins clarify the process here? thx. I found this post on the difference http://superuser.com/questions/756999/whats-the-difference-between-docker-stop-and-docker-kill And as CraziFuzzy suggested, I think the WebUI should have a "STOP" that sends 'docker stop' and a "FORCE STOP" that sends 'docker kill'. Quote Link to comment
CraziFuzzy Posted October 29, 2016 Author Share Posted October 29, 2016 So after a few more tests, I can confirm that the UI STOP command does NOT sent the stop command to docker. I can't believe this is expected behavior, and really should not even be considered acceptable behavior, and can be quite dangerous depending on the tasks in progress at the time. Quote Link to comment
CraziFuzzy Posted October 29, 2016 Author Share Posted October 29, 2016 Went ahead and issued a defect report for this. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.