-
Notifications
You must be signed in to change notification settings - Fork 854
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Watchtower now just removing containers and putting random stuff in it's place #1812
Comments
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! 🙏 |
You should be able to retrieve the logs from the previous run. Just running |
What time zone is 3 AM in? It could be because of a prior bug that I fixed yesterday that caused watchtower to crash, leaving a temporary container (the random one). |
This is CEST +2
|
The containers being removed is the same issue as #1809 (and has been resolved), and the randomly named containers should be the old Watchtower container (check its logs) which couldn't be removed, as also reported in that issue. |
Issue is now resolved - #1835 |
Describe the bug
I have used watchtower for years now without issue but suddenly it started doing weird things. My plex container was suddenly gone one morning and this new container was in it's place (see image)
I am on the DEV branch and have it set to run at 3 AM every morning.
Also note that the image used to create this odd weird container was containrrr/watchtower:latest-dev
Steps to reproduce
Set up watchtower on the dev branch
Set it to run at 3 am at night
Watch the mayhem the next morning
Expected behavior
It should recreate the plex container with the latest image
Screenshots
Environment
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: