Watchtower: Gotify container self-removed when update

[SAOPP]

Describe the bug
Gotify server container self-remove by watchtower when Gotify got update

To Reproduce
Steps to reproduce the behavior:
Add Gotify container to watch in Watchtower

Environment

• Platform
• Architecture
• Docker version

Logs from running watchtower with the --debug option

Additional context
Second time I'm faced with this issue, when Watchtower is remove gotify's container during update process of it. In other words, Watchtower start to update process, but can't redeploy the Gotify, and why it's happens I don;t know, because I don;t have any logs from Watchtower container now.

I hope it's could be simply reproduce by deploying old version of Gotify and start Watchtower to monitor this container for updates. I think result will be identical to my.

[github-actions[bot]]

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

[simskij]

Hi there and thank you for your report!

Would you mind trying to reproduce this with the —debug option enabled and then attach your logs to the issue?

Thanks 🙏🏻

[SAOPP]

Yes sure, I just forgot about logs, I have option -debug enabled, and just fast redeployed watchtower without gotify container monitor, and my logs is gone... Okay I'm try once again. Thanks u anyway.

[simskij]

Any news on this, @SAOPP? 😄

[SAOPP]

Hey! Sorry I missed this topic. :) I move Gotify to manual updates... need to check it.

[simskij]

No worries. I'll leave this open for a couple of more weeks then. :)

[SAOPP]

Okay. Thanks.

[simskij]

Closing this issue due to lack of activity. If this continues to be a problem, please open a new issue. Thank you! 🙏🏼

[devbots-lock-issue[bot]]

To avoid important communication to get lost in a closed issues no one monitors, I'll go ahead and lock this issue. If you want to continue the discussion, please open a new issue. Thank you! 🙏🏼