Error message - cannot kill container, no such container

Describe the bug

For the past few weeks I’ve been getting this error message in the logs for every container which has attempted to update:

“level= error msg= Error response from daemon: Cannot kill container:: No such container: ”

The log then reports the updates as failed however I believe it is successfully updating the containers and functioning fine. There is a new container running which is up to date and there are no leftover containers afterwards.

My docker config is standard and unchanged, running on latest unraid on a bridge network. Only thing I can think of which has changed was that I did run a duplicate watchtower container briefly (which stopped my current instance), but I have since deleted this container. I’ve tried recreating the new container but this doesn’t help.

Debug logs from before the error message seem to suggest the new image is pulled before the current container is being stopped and I’m wondering if perhaps the original container is being removed before the stop command is being sent? Any other ideas?

Steps to reproduce

Run watchtower
See error

Expected behavior

No error message

Screenshots

No response

Environment

Platform - unraid, latest stable 6.12.13

Your logs

E.g.

time=
2024-11-06T05:03:01+08:00
level=
info
msg=
Stopping /maintainerr (aa9244ba1614) with SIGTERM
time=
2024-11-06T05:03:01+08:00
level=
error
msg=
Error response from daemon: Cannot kill container: aa9244ba1614c5f959235c1d6feb71dc8fe2b6de50c1e0a7f9f3be9fd2a6dd61: No such container: aa9244ba1614c5f959235c1d6feb71dc8fe2b6de50c1e0a7f9f3be9fd2a6dd61
time=
2024-11-06T05:03:01+08:00
level=
debug
msg=
This is the watchtower container /watchtower
time=
2024-11-06T05:03:01+08:00
level=
info
msg=
Session done
Failed=
1
Scanned=
34
Updated=
0
notify=
no

Additional context

No response

containrrr / watchtower