Skip to content
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

Open
Spillebulle opened this issue Oct 24, 2023 · 6 comments

Comments

@Spillebulle
Copy link

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

image

Environment

  • Platform
  • Architecture
  • Docker Version

Your logs

I don't want to run it again as it would screw up my containers

Additional context

No response

@github-actions
Copy link

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

@piksel
Copy link
Member

piksel commented Oct 24, 2023

You should be able to retrieve the logs from the previous run. Just running docker logs watchtower or similar should show them. We don't have much to go on otherwise...

@piksel
Copy link
Member

piksel commented Oct 24, 2023

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).

@Spillebulle
Copy link
Author

Spillebulle commented Oct 24, 2023

This is CEST +2

time="2023-10-24T03:00:36+02:00" level=info msg="Watchtower v1.6.0-12-g3d1ed23"
time="2023-10-24T03:00:36+02:00" level=info msg="Using no notifications"
time="2023-10-24T03:00:36+02:00" level=info msg="Checking all containers (except explicitly disabled with label)"
time="2023-10-24T03:00:36+02:00" level=info msg="Scheduling first run: 2023-10-25 03:00:00 +0200 CEST"
time="2023-10-24T03:00:36+02:00" level=info msg="Note that the first check will be performed in 23 hours, 59 minutes, 23 seconds"
time="2023-10-24T10:24:13+02:00" level=info msg="Waiting for running update to be finished..."
time="2023-10-24T16:15:38+02:00" level=info msg="Watchtower v1.6.0-12-g3d1ed23"
time="2023-10-24T16:15:38+02:00" level=info msg="Using no notifications"
time="2023-10-24T16:15:38+02:00" level=info msg="Checking all containers (except explicitly disabled with label)"
time="2023-10-24T16:15:38+02:00" level=info msg="Scheduling first run: 2023-10-25 03:00:00 +0200 CEST"
time="2023-10-24T16:15:38+02:00" level=info msg="Note that the first check will be performed in 10 hours, 44 minutes, 21 seconds"

@ilike2burnthing
Copy link
Contributor

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.

@ilike2burnthing
Copy link
Contributor

Issue is now resolved - #1835

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants