Automatic image updates for Coolify services, carried out by Coolify itself.
1.9K
Automatic image updates for your Coolify services, carried out by Coolify itself.
coolify-watchtower checks the images of the services you choose, on a schedule you set per service. When a registry has a newer image, it asks Coolify to restart that service with the latest image. Coolify does the update, so it lands in the service's deployment history like any other deployment. Docker access is read-only, through a socket proxy.
Full documentation, source and issues: github.com/KimTholstorf/coolify-watchtower
read and deploy permissions.docker-compose.dockerhub.yml. Leave Connect to Predefined Network off.COOLIFY_TOKEN under Environment Variables and deploy. Everything else has a default.watchtower with the command true. Its frequency is the update schedule, e.g. 30 4 * * * for every day at 04:30.Services (compose and one-click) and Docker Image applications are supported. Notifications can go to Discord or ntfy, and coolify-watchtower keeps itself up to date too.
| Tag | Meaning |
|---|---|
latest | the newest release |
1.7.1, 1.7, 1 | a specific release, minor or major version |
Images are built for linux/amd64 and linux/arm64, and are identical to those on ghcr.io/kimtholstorf/coolify-watchtower.
MIT. coolify-watchtower isn't affiliated with Coolify or Watchtower.
Content type
Image
Digest
sha256:c49839777…
Size
16.2 MB
Last updated
about 1 month ago
docker pull kimtholstorf/coolify-watchtower