nils måsén

It's worse because it doesn't use the container-specified signal, sends a kill signal if it doesn't respond, but doesn't wait for the container to stop. The removal of the container...

On the note of alternatives: There is an attempt to standardize the metadata in container labels called [OpenContainers metadata labels](https://github.com/opencontainers/image-spec/blob/main/annotations.md), and support for adding them to the notifications are in...

I have been thinking about how to solve this, but have not come up with a non-janky solution yet... Either: 1. Start new watchtower with no port forwarding and some...

No, because it's the docker port forwarding that is the problem. Two containers cannot have ports forwarded to the same port on the host.

Hmm, that should be the normal behaviour of watchtower... Not sure how it misses the second one. How are you running watchtower, and what does the report say after a...

Well, it seems like it just ignores the second container for some reason, and then when it tries to remove the old image for container 1 it can't since it's...

Maybe the second container was stopped in the first run? You can include stopped containers using `--include-stopped`. Otherwise, we can't do much without logs from when it didn't work. 🤷‍♀️...

None of these are errors. The `level=debug` indicates that those are just debug messages, and should not be treated as errors. The last messages for example, just tells you that...

This has been suggested before, but no one has implemented such a feature yet. It would probably be easier to do using #1231.

Well, there is the `--porcelain v1` flag that you can use to write a machine-readable to stdout after each run. You can also add another notification service to push that...