`` Stopping old container /usr/bin/docker stop -t 10 app `` This takes forever, any ideas how to solve it? I tried to restart the docker service & Physical Server but I still can’t stop the container. I just find this: Continuing the discussion from Runsv hanging on Docker container shutdown: [image] New image is out now and will resolve this issue. but, if I can’t stop old container how can I rebuild with the new image?

Reboot your machine so Discourse is running normally. Run docker ps to get the container ID. If there are multiple, you need to find the right one. Then, run docker kill to kill the container. While stopping is broken, killing works – so violence does help here :slight_smile: Then, simply rebuild as usual.

[image] fefrei: run docker kill to kill the container thanks, but, docker kill also takes forever… :confused:

Hm, then I’m out of ideas. Are you certain you rebooted your server beforehand? Any try to stop the container will most likely leave it unstoppable and needing 100% CPU. Killing only worked for me while the container was running normally.

[image] fefrei: Killing only worked for me while the container was running normally. thanks, I restarted my Physical Server, than worked!

Can't stop container

Product Support

freemangl (无限星辰) February 1, 2016, 3:24pm 3

thanks, but,
docker kill also takes forever…

Topic		Replies	Views
Emergency help - freeCodeCamp Discourse down Self-hosting	18	2511	February 22, 2017
Docker problem after machine restart Product Support	2	2333	September 22, 2015
Cannot rebuild following site failure: "postgres already running" Self-hosting	14	5319	September 17, 2015
Rebuild freezing when attempting to stop container Self-hosting	3	991	August 8, 2022
How to fix "container is marked for removal and cannot be started" without reboot Self-hosting hosting	1	25060	December 17, 2019

Can't stop container

Related topics