NikTheDusky, 3 months ago

@cato meanwhile me: lets watchtower auto update all of my container images every night

cato, 3 months ago

@NikTheDusky why would you do that

NikTheDusky, 3 months ago

@cato less manual maintenance and works 99% of the time

cato, 3 months ago

Turns out using "latest" doesn't pull on restart, you have to manually do a pull. That explains why, despite ueing "latest", it was a version from 2022. Interesting

seatsea, 3 months ago

@cato yeah it’s an odd practice, but also manually choosing a version each time feels clunky too

cato, 3 months ago

@seatsea I'd rather update all my containers when I get to it every few months that have stuff break

LeoDJ, 3 months ago

@cato
not on restart, but on the next docker-compose up, e.g. if you updated some minor config thing

cato, 3 months ago

@LeoDJ no no, that's what I meant by restart. No, you have to execute an actual pull command

LeoDJ, 3 months ago

@cato
Yes, but iirc it recreates the container (and thus pulls the new image) if you made a change to the yaml (like e.g. change a port or something other small).
But maybe I'm misremembering or it changed ^^"

cato, 3 months ago

@LeoDJ Ahh might be if you change the yaml