"/overseerr" is already in use by container "07f52dde559471279b585f9ce267bf4189ab3361470122e03675c1634706c46c". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

The command failed.

Getting this for every docker and a handful aren't working at all. Do I need to delete my docker img?

 

This came about after my cache kept filling up. Ended up removing a few Dockers and updating to the latest OS at the same time.

r510-diagnostics-20221027-1416.zip

Edited October 27, 20223 yr by tonsofguns

Try going to settings and turning off the docker service and then start it back up again. if that does not work reboot the server, usually one of those will fix the issue.

1 hour ago, philliphartmanjr said:

Try going to settings and turning off the docker service and then start it back up again. if that does not work reboot the server, usually one of those will fix the issue.

Did both of these. Docker service failed to start on reboot. Disabled and enabled docker and still won't start. Attempting another reboot.

 

Edit: looks like my cache is completely full again. Last time it was my unify logs going crazy. I removed that docker. Won't be able to see what's causing this one until I get home though. Seems like some kinda OS issue if it's happening with different Dockers though. Been running the same ones for a long time. Haven't changed anything at all before all this started.

Edited October 27, 20223 yr by tonsofguns

Looking through you logs it appears there is an issue with one of your plugins.

level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header"

I would check them and make sure they are all up to date nerdpack was one of them it is not compatible with your unraid version. your cache I saw you mentioned that you can schedule the mover to run. Your log also showed you do not have Unassigned Devices Plus. there is also a few dockers out of date I would fix these issues first and then reboot

I had similar issue, dockers throwing errors while updating. Turned out my /system share did not have enough free disk space. I moved it to cache drive with tons of free space and it works just fine.

I use user script to update sometimes.
 

docker images | grep -v ^REPO | sed 's/ \+/:/g' | cut -d: -f1,2 | xargs -L1 docker pull

I also use ca auto update tool to assist.

Do you have nay orphan images?
click advance and scroll to the bottom. you should not have any orphan images.
--You may need to run docker prune to clear and clean the docker system..
look in to docker prune system all <dangerous command but will delete non-running stuff

sometimes the logs get filled with docker img and the log kills the abilty to update the dockers on unraid.

settings > docker > image size increase it.
^sometimes you have to delete that image file as docker that don't have a dat path will fill it up with temp data within the image.

You can delete the disk image. (this will delete the temp data and all dockers in the docker tab...) <This is not data loss!

[unless you have misconfigured dockers and important data in the temp file.]
make a new one click add container and select the docker you were running to re add them back to unraid. (a re-added will downloaded the lattest image.

install user script plugin and run some default scripts that came with it:

On 10/27/2022 at 1:13 PM, tonsofguns said:

"/overseerr" is already in use by container "07f52dde559471279b585f9ce267bf4189ab3361470122e03675c1634706c46c". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

The command failed.

Getting this for every docker and a handful aren't working at all. Do I need to delete my docker img?

 

This came about after my cache kept filling up. Ended up removing a few Dockers and updating to the latest OS at the same time.

r510-diagnostics-20221027-1416.zip 158.44 kB · 2 downloads

you have a docker name overseerr in the docker list that is either running , stopped or orphaned.
If you are trying to run multiple of the same docker you will need to have a different name for the docker running.