nils måsén

Sure, the telegram service is similar and loops over its targets (`chats`) when sending: https://github.com/containrrr/shoutrrr/blob/52149dcefc8eef26627cc5f48a0c3997280bc879/pkg/services/telegram/telegram.go#L25 It's configured using the `key` tag (the second arg `channels` is an alias for backwards...

The `.UseHTML` is set if it's in the service URL (`&usehtml=yes`). The config is updated here: https://github.com/containrrr/shoutrrr/blob/a59c927fa212f22f3330e2192a66fc2dda1634c2/pkg/services/smtp/smtp.go#L49-L51 How are you using shoutrrr? As a library or in another software? There...

> Even checking out to the last commit in v0.8.0 gave me the same error. > The same credential works when I am checked out to v0.8.0 tag though. I'm...

The tag is on another branch, but there are no changes to the `smtp` service. Perhaps there is something else on the `latest` branch that makes a difference... Actually, I...

I still think marking it as not stale may have consequences for other interactions, like notifications and metrics. I'll take a look when I am at a computer.

I started making some changes to your branch but it ended up mostly being a cleanup of the current `update` code, so I made it a separate PR (#1895). It...

You can simply add a (unique) scope label to each of the watchtower instances. To be clear, don't add the `--scope` argument, just the label. This will prevent the watchtower...

Yeah, seems to be related to apparmor permissions. Perhaps @simskij has some insights?

This bug contains some more info (not on Ubuntu 23.10, so I cannot test it unfortunately): https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039294 I guess we need to allow watchtower/docker to send signals using an apparmor...

`docker pull` doesn't start a container. How are you running watchtower? `arm64v8-latest` was updated along with the other tags to v1.7.1 two weeks ago: https://hub.docker.com/r/containrrr/watchtower/tags