Skip to content
Discussion options

You must be logged in to vote

This is normal behavior, as it's part of Watchtower's self-update process to rename the old Watchtower container to a random Docker container name before starting the new Watchtower container.

Replies: 1 comment 4 replies

Comment options

You must be logged in to vote
4 replies
@mastercodefu
Comment options

@Nindaleth
Comment options

@nicholas-fedor
Comment options

@mastercodefu
Comment options

Answer selected by nicholas-fedor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants