monitor_docker icon indicating copy to clipboard operation
monitor_docker copied to clipboard

Restart needed when any docker container is re-created (reopening #143)

Open LordShadowen opened this issue 9 months ago • 4 comments

As the title says, I have the exact same issue as it was reported on #143. It got closed as solved, but it still happens to me. When Watchtower updates a running container, the logs are full of errors "Container not available anymore"

I'm on latest (1.19). Not sure if it makes a difference, but I'm connecting through docker-proxy (url: tcp://[proxy]). Could that be it?

LordShadowen avatar Mar 14 '25 21:03 LordShadowen

Try 1.20b3 please.

ualex73 avatar Apr 06 '25 18:04 ualex73

the issue seems to be resolved in 1.20b3

briodan avatar Apr 09 '25 16:04 briodan

sorry, didn't realize there was a beta version to try... yes, it seems to fix it

LordShadowen avatar Apr 14 '25 13:04 LordShadowen

I think I'm seeing the same thing on 1.20b3 with podman. To reproduce:

  • Start all containers (Integration shows all containers as running, as it should)
  • Stop a container (Integration shows "unknown" for the stopped container, ok, but is "stopped" a possibility?)
  • Restart the container (Integration continues to show "unknown" indefinitely)
  • Restart Home Assistant (Integration shows the restarted container as running, correctly; other stopped containers still appear "unknown")

Log errors:

  • This one apparently occurs once per minute after stopping a container:
This error originated from a custom integration.

Logger: custom_components.monitor_docker.helpers
Source: custom_components/monitor_docker/helpers.py:938
integration: Monitor Docker (documentation, issues)
First occurred: September 1, 2025 at 12:42:00 PM (1803 occurrences)
Last logged: 6:38:03 PM

[Podman] openwakeword: Container not available anymore (3a) (DockerError(404, 'no container with name or ID "144d143a29eae537db98c76b18d896beff396dcd4c0db7c6dfe24f7d1dd895b9" found: no such container')). Retry in 60 seconds
[Podman] piper: Container not available anymore (3a) (DockerError(404, 'no container with name or ID "a0766711186a7a2ff2b52b49842fcd048614674fbfe3772c5c1a67667aae60b8" found: no such container')). Retry in 60 seconds
  • This one shows up upon a container restart:
This error originated from a custom integration.

Logger: custom_components.monitor_docker.helpers
Source: custom_components/monitor_docker/helpers.py:574
integration: Monitor Docker (documentation, issues)
First occurred: September 1, 2025 at 12:42:29 PM (9 occurrences)
Last logged: 6:38:16 PM

[Podman] openwakeword: Container already monitored
[Podman] piper: Container already monitored

wixoff avatar Sep 02 '25 22:09 wixoff