You must log in or register to comment.
It’s similar to my own setup. I just do it in kubernetes instead of docker. One thing you can consider is a CI that runs renovate on a schedule to PR you when it finds new container image versions.
Here’s my setup so you can take some inspiration if you want.
https://github.com/rafaribe/home-ops/blob/main/.github/workflows/schedule-renovate.yaml
Nice, the GitHub link I posted is slightly cleaned up and orphaned from my actual homelab repo. Not sure if I can use this, because to update these services I need to run
systemctl restart, or hope that watchtower eventually supports docker-compose.So is does your homelab respond to changes in that repo?
Watchtower works fine with docker compose. I’m not sure what you’re trying to say.
As far as I could tell, you can use docker-compose to manage your running of watchtower, but it has issues working with containers that were started via docker-compose: https://github.com/containrrr/watchtower/issues/1019
Still not following. Are you setting up containers with portainer or something? My whole docker setup is in one docker-compose.yml. I use docker compose, not docker-compose. Maybe that’s the issue?
Edit: that link is about running docker in Windows 10.
I think I’m going to have to spin up a VM to understand why you’re doing things the way they are, instead of using a .env file with the docker-compose.yml, or docker secrets. The built-in way to run containers is very straightforward, and it seems at first glance that you’re making it a bit more complicated than it needs to be. There’s no need to mess with systemctl at all, for example.