watchtower: The latest release creates bad containers

Describe the bug

Creates new containers for watchtower after last released version of docker image

Steps to reproduce

  • Configured watchtower
  • update watchtower to last version of docker image and reload
  • see that bug

Expected behavior

Just update 1 container (watchtower’s container)

Screenshots

image image image

Environment

  • Ubuntu server 22.04
  • x64

Your logs

-

Additional context

No response

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Reactions: 2
  • Comments: 20 (10 by maintainers)

Most upvoted comments

v1.7.1 is now released which should fix the issue.

Yep, back up and running without duplicates. Thanks.

yes fixed with 1.7.1 - thanks a lot!

That’s odd because we had tons of watchtower containers. If anyone’s curious, you can kill them all at once with:

docker kill $(docker ps | grep watchtower | sed 's/ .*//')

PS: you’re right, we had this folder and no clue why. Unrelated issue.

@JA16122000 docker hub is having service degradation right now: https://www.dockerstatus.com/