Error message - cannot kill container, no such container

[stunrelay]

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?

###EDIT####
Update - yesterday’s watchtower schedule successfully updated my immich stack (which is managed by Unraids docker compose plugin) without an error message. It still produced an error message when updating the containers which are managed by Unraids default docker management dockerman (docker CLI) however. See log example.

Steps to reproduce

1. Run watchtower
2. See error

Expected behavior

No error message

Screenshots

No response

Environment

• Platform - Unraid, latest stable 6.12.13
• Docker - 24.0.9
  Config:
  docker run
    -d
    --name='watchtower'
    --net='bridge'
    --pids-limit 2048
    -e TZ="TZ***"
    -e HOST_OS="Unraid"
    -e HOST_HOSTNAME="NAME***"
    -e HOST_CONTAINERNAME="watchtower"
    -e 'WATCHTOWER_CLEANUP'='true'
    -e 'WATCHTOWER_INCLUDE_STOPPED'='true'
    -e 'WATCHTOWER_SCHEDULE'='0 0 5 * * '
    -e 'WATCHTOWER_REVIVE_STOPPPED'='false'
    -e 'WATCHTOWER_NOTIFICATION_REPORT'='true'
    -e 'WATCHTOWER_NOTIFICATION_URL'='URL**'
    -e 'WATCHTOWER_DEBUG'='true'
    -l net.unraid.docker.managed=dockerman
    -l net.unraid.docker.icon='https://containrrr.dev/watchtower/images/logo-450px.png'
    -v '/var/run/docker.sock':'/var/run/docker.sock':'rw' 'containrrr/watchtower'
  803ad909ef71c1a48f33a6387603567b258aad9a94254472e69e0617a3e58829

Your logs

PARTIAL LOGS TO BE CONCISE:
E.g. 1 

    * 		time=
2024-11-07T05:13:47+08:00
level=
debug
msg=
Pulling image
container=
/AdGuard-Home
image=
adguard/adguardhome:latest
* 		


    * 		time=
2024-11-07T05:13:52+08:00
level=
info
msg=
Found new adguard/adguardhome:latest image (f3f766c536f5)
    * 



E.g. 2

    * 		time=
2024-11-07T05:00:36+08:00
level=
debug
msg=
Pulling image
container=
/immich_server
image=
ghcr.io/immich-app/immich-server:release
* 		


    * 		time=
2024-11-07T05:08:49+08:00
level=
info
msg=
Found new ghcr.io/immich-app/immich-server:release image (fd58d779b0a6)
    * 



E.g. 3
* 
    * 		time=
2024-11-07T05:14:44+08:00
level=
info
msg=
Stopping /AdGuard-Home (b147d45b00b6) with SIGTERM
* 		


    * 		time=
2024-11-07T05:14:44+08:00
level=
error
msg=
Error response from daemon: Cannot kill container: b147d45b00b6672100b8d4dcba3c3590e46549804797cf6f06fdd5535ed10118: No such container: b147d45b00b6672100b8d4dcba3c3590e46549804797cf6f06fdd5535ed10118
* 		


    * 		time=
2024-11-07T05:14:44+08:00
level=
info
msg=
Stopping /bazarr (d6c251b96914) with SIGTERM
* 		


    * 		time=
2024-11-07T05:14:44+08:00
level=
error
msg=
Error response from daemon: Cannot kill container: d6c251b969149163330b6817e1a49718efed0448933c9adc4cb688ce5a1f0bd3: No such container: d6c251b969149163330b6817e1a49718efed0448933c9adc4cb688ce5a1f0bd3
* 		


    * 		time=
2024-11-07T05:14:44+08:00
level=
info
msg=
Stopping /immich_machine_learning (8f17a7c6267c) with SIGTERM
* 		


    * 		time=
2024-11-07T05:14:46+08:00
level=
debug
msg=
Removing container 8f17a7c6267c
* 		


    * 		time=
2024-11-07T05:14:46+08:00
level=
info
msg=
Stopping /immich_server (1c556b39a83c) with SIGTERM
* 		


    * 		time=
2024-11-07T05:14:48+08:00
level=
debug
msg=
Removing container 1c556b39a83c
* 		


    * 		time=
2024-11-07T05:14:48+08:00
level=
debug
msg=
This is the watchtower container /watchtower
* 		


    * 		time=
2024-11-07T05:14:48+08:00
level=
info
msg=
Creating /immich_server
* 		


    * 		time=
2024-11-07T05:14:49+08:00
level=
debug
msg=
Starting container /immich_server (32e275b2dd5d)
* 		


    * 		time=
2024-11-07T05:14:51+08:00
level=
info
msg=
Creating /immich_machine_learning
* 		


    * 		time=
2024-11-07T05:14:52+08:00
level=
debug
msg=
Starting container /immich_machine_learning (821c43ffd59e)
* 		


    * 		time=
2024-11-07T05:14:55+08:00
level=
info
msg=
Removing image 54d4f058d5f0
* 		


    * 		time=
2024-11-07T05:14:57+08:00
level=
debug
msg=
Image removal completed
deleted=
54d4f058d5f0, b239ce8f5521, c0ef5bdcaea7, 3c2c040bdc4b, 2db6cd020ffd, 1e60dbb0c88c, 00c9b7542b07, [187781020239](tel:187781020239), e18c9a2bbaf6, 5fd9602f4ca0, ca2c628dd1e8, 4c4b0ebbaa6b, 0f25835c66d2, 0caf19fd5d33, dad15046b182, 5e6c51ba0d52, 8ea134419814, 4489fbf126d8, 939b07272207, 5b34c13fb426, 5b8e5f4c16f7, c8be68bd4f36, f5385e716440, edf0974c944a
untagged=
ghcr.io/immich-app/immich-server@sha256:d63feeee7a41
* 		


    * 		time=
2024-11-07T05:14:57+08:00
level=
info
msg=
Removing image 52eb9a353af0
* 		


    * 		time=
2024-11-07T05:14:58+08:00
level=
debug
msg=
Image removal completed
deleted=
52eb9a353af0, fd7252a683dd, f629d7709690, c2eec5693c3c, 1838e92328f5, 2da71504970e, 2d33b52fad37, 192216afaaa9
untagged=
ghcr.io/immich-app/immich-machine-learning@sha256:e8c416445db6
* 		


    * 		time=
2024-11-07T05:14:58+08:00
level=
info
msg=
Session done
Failed=
2
Scanned=
34
Updated=
2
notify=
no
* 		


    * 		time=
2024-11-07T05:14:58+08:00
level=
debug
msg=
Scheduled next run: 2024-11-08 05:00:00 +0800 AWST
    *

### Additional context

[github-actions]

Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏