e3d12fd040
|
3 weeks ago | |
|---|---|---|
| .devbots | 6 years ago | |
| .github | 3 weeks ago | |
| cmd | 3 weeks ago | |
| dockerfiles | 2 years ago | |
| docs | 3 weeks ago | |
| grafana | 4 years ago | |
| internal | 3 weeks ago | |
| pkg | 3 weeks ago | |
| prometheus | 5 years ago | |
| scripts | 2 years ago | |
| tplprev | 2 years ago | |
| .all-contributorsrc | 2 years ago | |
| .codacy.yml | 7 years ago | |
| .editorconfig | 3 years ago | |
| .gitignore | 2 years ago | |
| CHANGELOG.md | 3 weeks ago | |
| CONTRIBUTING.md | 6 years ago | |
| LICENSE.md | 8 years ago | |
| README.md | 3 weeks ago | |
| SECURITY.md | 5 years ago | |
| build.sh | 4 years ago | |
| code_of_conduct.md | 6 years ago | |
| docker-compose.yml | 5 years ago | |
| docs-requirements.txt | 4 years ago | |
| go.mod | 2 years ago | |
| go.sum | 2 years ago | |
| gopher-watchtower.png | 6 years ago | |
| goreleaser.yml | 5 years ago | |
| logo.png | 6 years ago | |
| main.go | 6 years ago | |
| mkdocs.yml | 3 years ago | |
| oryxBuildBinary | 2 years ago | |
README.md
Watchtower
A process for automating Docker container base image updates.
Quick Start
With watchtower you can update the running version of your containerized app simply by pushing a new image to the Docker Hub or your own image registry.
Watchtower will pull down your new image, gracefully shut down your existing container and restart it with the same options that were used when it was deployed initially. Run the watchtower container with the following command:
$ docker run --detach \
--name watchtower \
--volume /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower
Watchtower is intended to be used in homelabs, media centers, local dev environments, and similar. We do not recommend using Watchtower in a commercial or production environment. If that is you, you should be looking into using Kubernetes. If that feels like too big a step for you, please look into solutions like MicroK8s and k3s that take away a lot of the toil of running a Kubernetes cluster.
Using a custom registry CA (private registries)
If you run Watchtower against a private registry that uses a custom TLS certificate, provide the CA bundle and enable validation at startup so Watchtower fails fast on misconfiguration:
$ docker run --detach \
--name watchtower \
--volume /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower \
--registry-ca /etc/ssl/certs/my-registry-ca.pem \
--registry-ca-validate=true
Prefer providing a CA bundle and enabling --registry-ca-validate over disabling TLS verification with --insecure-registry in production environments.
Documentation
The full documentation is available at https://containrrr.dev/watchtower.
Contributors
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!