I have quite a lot of Docker Compose stacks spread across many different home lab hosts. I realized the difficult part was not rolling out containers. It was ke

I have quite a lot of Docker Compose stacks spread across many different home lab hosts. I realized the difficult part was not rolling out containers. It was keeping them updated over time. I kept SSHing into individual servers, finding the right Compose directory, pulling new images, and then redeploying my stacks. Then, once they restart, I check whether everything came back healthy. In this post I walk through how I started using Komodo to automate part of that workflow. With it, I can monitor container image updates, and automate redeployments. It also allows you to import your Compose stacks, and you can use deployments that are stored in your Git repos without having to change your Docker Compose. I also look at the difference between Poll for Updates, Auto Update, the global update schedule. Also, see how Komodo can pull from Git when you make changes. Curious how others are managing this once Docker Compose environments go beyond a single host.