Rolling restart ignores monitor-only label

[jvkohler]

Describe the bug

Enabling rolling restarts with incompatible containers that include com.centurylinklabs.watchtower.monitor-only=true results in abort.

Steps to reproduce

1. Set WATCHTOWER_ROLLING_RESTART=true in docker compose for watchtower
2. Set label com.centurylinklabs.watchtower.monitor-only=true on containers with a service dependency, like something using gluetun.
3. Start watchtower

Expected behavior

Rolling restart only analyses dependency chain of full update enabled containers

Screenshots

No response

Environment

containrrr/watchtower@sha256:e7dd50d07b86c380dd53caeb7778da052d1a8fc2c606644a419afa35e9f5691e
Docker 27.1.2 on x64 Debian Bookworm

Your logs

time="2024-10-01T23:24:14-06:00" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized."

time="2024-10-01T23:24:15-06:00" level=debug msg="Making sure everything is sane before starting"

time="2024-10-01T23:24:15-06:00" level=debug msg="Retrieving running containers"

time="2024-10-01T23:24:15-06:00" level=error msg="\"/arr-flaresolverr\" is depending on at least one other container. This is not compatible with rolling restarts"

time="2024-10-01T23:24:15-06:00" level=info msg="Waiting for the notification goroutine to finish" notify=no

Additional context

No response

[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! 🙏