One of my docker containers seems to have bugged out. At first it wouldn't start up anymore, I didn't really care about the container, so I ignored it. After a while docker it's self started to get really laggy, so I stopped and restarted the docker service, but docker wouldn't start up again. I did a bunch of searching, there weren't any terminals open or anything like that, it seemed tied to the one container being busy. I tried to restart unraid, I always shut down the array first manually first, but it even got stuck shutting down the array because of the busy container. I rebooted unraid and everything come back up fine, tried to delete the problem container, and now it's stuck in a "Removal in Progress" state.

 

I've tried to search a bunch of CLI ways how to kill it, but none of the solutions I've found have worked so far. Attached are the diagnostics. I don't care about the container in question at all, just want to get rid of it without messing anything else up. Thanks for the help!

tiger-diagnostics-20250426-1052.zip

https://docs.docker.com/reference/cli/docker/system/prune/

 

docker system prune

 

 

25 minutes ago, bmartino1 said:

https://docs.docker.com/reference/cli/docker/system/prune/

 

docker system prune

 

 

Adding --volumes got rid of some old unrelated stuff, but didn't not get rid of the Removal in Process container. Thanks though.

you will have to first kill any autostart docker.

Then go to settings docker turn off

(this is to kill all running dockers)

and reboot if still in that state and run the docker commands to prune...

Turn docker on (No docker should be running)

docekr ps

Then run the prune commands to 

prune will not kill a running docker stuck is still running...
 

a docker maintenance script... 

#!/bin/bash

# Script to prune dangling Docker images and clean up

echo "Starting Docker maintenance..."

#Docker Unraid Check if dangling images exist
docker rmi $(docker images --quiet --filter "dangling=true")
#docker builder prune -f

# Prune dangling Docker images
echo "Pruning dangling Docker images..."
docker image prune -f

# Automatically prune unused containers, networks, and volumes
echo "Pruning unused containers, networks, and volumes..."
docker system prune -f --volumes

echo "Finished Docker maintenance."

 

look into dangling images...

I'll need to try again later because my first attempt didn't work.

 

After making sure nothing would auto start, and a fresh reboot of unraid, docker started up, and the problem container was in a "dead" state. I assumed I should start all containers I want to keep so the prune doesn't delete them.

 

The prune didn't find the problem container to delete, and when I checked the docker tab again, the problem container was back the in the "removal in process" state.

 

Is there any way to directly delete the offending image form the array before docker is started?

 

Thanks for the help! 

Correct the batch script should be ran above but it will delete any non-running docker. I sometimes have to do these when dev building and pushing dockers to docker hub.

even if it was deleted in the docker web ui add container click apply to bring it back as this will cause a docker pull again.

 

I ended up deleting my image, changing to overlay2 and reinstalling everything. So far so good.