An idea for a related topic. Use the pre-update hooks to make a backup of the container volumes before an upgrade of the container. Because often a new version has code running that alters the data and there is no downgrade possible. Hooks to automatically make backups right before a container image upgrade is an nice addition to a regular backup schedule.
Are there any other tutorial that dives a bit deeper into how to configure, for example if you have to let watchtower watch multiple stack in portainer that are from different registry with different access token? All these tutorial seem to be very identical to other tutorials on RU-vid
I’m surprised that you weren’t using gitops to configure and deploy containers! Good video though. I’m in the planning phase of deploying watchtower so I’m learning what configuration options are. I already started writing the github workflow flow to deploy it , but I’m far from committing and pushing that file to github!
Thanks for your great videos... I have one question. In 4:55 you said that if we specify a version tag, Watchtower does not update the image. Isn't that wrong? If that is right, then Watchtower almost has no use, because we barely use latest tag in production.
What would Watchtower update the container to if you've specified a specific version? The whole point of the version number is to keep it a that version if the image ever needs re-pulled
Excuse my ignorance, you have to indicate a restart value, or the service having the scheduled schedule, it will execute itself, I ask if there is a docker restart, thanks
Hi there, great video, how would you add an exception to a docker-compose file? For example, I want to deploy Watchtower out but want to avoid it updating my PiHole.
how to have watchtower listen for a signal after successful docker image build in github actions and try to update image then and not just randomly on a cron?
First of all thanks for the helpful video. How do I handle container updates? I don't mean updating the base image when it changes, but applying regular security updates with apt. What in case of automatic security updates? Set up unattended-upgrades in each Docker container with appropriate update interval or automatically rebuild the image if Dockerfile contains a "RUN apt update && apt upgrade -y" statement or even include unattended-updates as RUN command in Dockerfile and rebuild the image each time? I'm wondering why I can't find many resources on this topic because it's so important. Can you (and/or someone) please cover this question?
I'm no expert but if I'm honest I've never heard of someone running package updates in a running container. You usually do it when building the image. From my point of view, that's like asking for annoying things to break that you probably won't be able to fix until the builder of the image releases an update - depending on the application/your knowledge. If you're building your images yourself and keep track of all dependencies then it's no biggie of course.
At 08:44, you run the command to schedule Watchtower, but it sits running (probably until it runs). How can you run that command so it drops back to the prompt, but is still scheduled? Thanks!
What about if you have docker-compose ? Everyone you restart the docker compose if not edited with lastest versions it will revert to what the version in docker compose is ?
That shouldn't make a difference. When you're using the :latest tag it should work the same for compose files as well. If you tagged a specific version, it won't be updated
@@christianlempa Does updating through Watchtower retain the full control by Portainer though? I'm hesitant to let it just go ham on my images and then find out that suddenly my stacks are decoupled or however you might call it.
@@AlexChama What many people do is set Watchtower to 'monitor only' mode and then it can email you when updates are available to your containers, and then you can manually action them as desired. For example if there's an upgrade to a new major version for a specific app you may want to run it manually as it has specific steps to follow post-update, like with Nextcloud. The variable to set Watchtower to monitor only mode in your docker compose file is: - WATCHTOWER_MONITOR_ONLY=true
Hi, im facing a issue to make watchtower work with my private repository on docker hub it can't authentify... someone has a idea how to make it work with your private repository ? thank you!
@@christianlempa Hi, thank you for your answer ! i already check that but i could not be able to connect it to my private repository :'( i must have done it not well
Hi Bro can you make a video on ansible playbook writing pattern in yaml. I have seen lot of videos but they don't explain the pattern there are lot of long spaces in the starting of sentences then there are hyphens in the sentences that too are starting from odd lines hence its getting confusing and difficult to understand not sure if it has a standard pattern/format. can you kindly explain this in the video i am not from a coding or a devops background
I need to have a look at this, but yea I'm working to extend my ansible boilerplates that are on my Github page. So you might want to take a look at :)
You should consider legal actions as your termination was clearly wrong. If people like you don't take stand, now do you expect regukar folks to do it? Suing the department and the state has nothing with not respecting people who fight fire. They also are being victimized.
@@christianlempa sorry for that. The comment was aimed for some othe video, and the youtube client somehow got confused and attached it to yours. Again, I appologize.
