By default, watchtower will monitor all containers running within the Docker daemon to which it is pointed (in most cases this +
By default, watchtower will monitor all containers running within the Docker daemon to which it is pointed (in most cases this
will be the local Docker daemon, but you can override it with the --host option described in the next section). However, you
can restrict watchtower to monitoring a subset of the running containers by specifying the container names as arguments when
launching watchtower.
By default, watchtower will watch all containers. However, sometimes only some containers should be updated.
+By default, watchtower will watch all containers. However, sometimes only some containers should be updated.
If you need to exclude some containers, set the com.centurylinklabs.watchtower.enable label to false.
LABEL com.centurylinklabs.watchtower.enable="false"
Watchtower is an application that will monitor your running Docker containers and watch for changes to the images that those containers were originally started from. If watchtower detects that an image has changed, it will automatically restart the container using the new image.
+Watchtower is an application that will monitor your running Docker containers and watch for changes to the images that those containers were originally started from. If watchtower detects that an image has changed, it will automatically restart the container using the new image.
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.
For example, let's say you were running watchtower along with an instance of centurylink/wetty-cli image:
$ docker ps
diff --git a/linked-containers/index.html b/linked-containers/index.html
index 2e1c925..f700110 100644
--- a/linked-containers/index.html
+++ b/linked-containers/index.html
@@ -1,2 +1,2 @@
-Linked containers - Watchtower Linked containers
Watchtower will detect if there are links between any of the running containers and ensure that things are stopped/started in a way that won't break any of the links. If an update is detected for one of the dependencies in a group of linked containers, watchtower will stop and start all of the containers in the correct order so that the application comes back up correctly.
+Linked containers - Watchtower Linked containers
Watchtower will detect if there are links between any of the running containers and ensure that things are stopped/started in a way that won't break any of the links. If an update is detected for one of the dependencies in a group of linked containers, watchtower will stop and start all of the containers in the correct order so that the application comes back up correctly.
For example, imagine you were running a mysql container and a wordpress container which had been linked to the mysql container. If watchtower were to detect that the mysql container required an update, it would first shut down the linked wordpress container followed by the mysql container. When restarting the containers it would handle mysql first and then wordpress to ensure that the link continued to work.
Notifications - Watchtower Skip to content Notifications¶
+Notifications - Watchtower Skip to content Notifications¶
Watchtower can send notifications when containers are updated. Notifications are sent via hooks in the logging system, logrus.
The types of notifications to send are passed via the comma-separated option --notifications (or corresponding environment variable WATCHTOWER_NOTIFICATIONS), which has the following valid values:
diff --git a/remote-hosts/index.html b/remote-hosts/index.html
index 35796e3..6a836ed 100644
--- a/remote-hosts/index.html
+++ b/remote-hosts/index.html
@@ -1,4 +1,4 @@
-Remote hosts - Watchtower Remote hosts
By default, watchtower is set-up to monitor the local Docker daemon (the same daemon running the watchtower container itself). However, it is possible to configure watchtower to monitor a remote Docker endpoint. When starting the watchtower container you can specify a remote Docker endpoint with either the --host flag or the DOCKER_HOST environment variable:
+Remote hosts - Watchtower Remote hosts
By default, watchtower is set-up to monitor the local Docker daemon (the same daemon running the watchtower container itself). However, it is possible to configure watchtower to monitor a remote Docker endpoint. When starting the watchtower container you can specify a remote Docker endpoint with either the --host flag or the DOCKER_HOST environment variable:
docker run -d \
--name watchtower \
containrrr/watchtower --host "tcp://10.0.1.2:2375"
diff --git a/secure-connections/index.html b/secure-connections/index.html
index 443146b..59ac19a 100644
--- a/secure-connections/index.html
+++ b/secure-connections/index.html
@@ -1,4 +1,4 @@
-Secure connections - Watchtower Secure connections
Watchtower is also capable of connecting to Docker endpoints which are protected by SSL/TLS. If you've used docker-machine to provision your remote Docker host, you simply need to volume mount the certificates generated by docker-machine into the watchtower container and optionally specify --tlsverify flag.
+Secure connections - Watchtower Secure connections
Watchtower is also capable of connecting to Docker endpoints which are protected by SSL/TLS. If you've used docker-machine to provision your remote Docker host, you simply need to volume mount the certificates generated by docker-machine into the watchtower container and optionally specify --tlsverify flag.
The docker-machine certificates for a particular host can be located by executing the docker-machine env command for the desired host (note the values for the DOCKER_HOST and DOCKER_CERT_PATH environment variables that are returned from this command). The directory containing the certificates for the remote host needs to be mounted into the watchtower container at /etc/ssl/docker.
With the certificates mounted into the watchtower container you need to specify the --tlsverify flag to enable verification of the certificate:
docker run -d \
diff --git a/sitemap.xml b/sitemap.xml
index 054f60d..a608a32 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,52 +1,52 @@
- http://localhost:8000/
+ http://containrrr.github.io/watchtower/
2019-06-01
daily
- http://localhost:8000/introduction/
+ http://containrrr.github.io/watchtower/introduction/
2019-06-01
daily
- http://localhost:8000/usage-overview/
+ http://containrrr.github.io/watchtower/usage-overview/
2019-06-01
daily
- http://localhost:8000/arguments/
+ http://containrrr.github.io/watchtower/arguments/
2019-06-01
daily
- http://localhost:8000/notifications/
+ http://containrrr.github.io/watchtower/notifications/
2019-06-01
daily
- http://localhost:8000/container-selection/
+ http://containrrr.github.io/watchtower/container-selection/
2019-06-01
daily
- http://localhost:8000/linked-containers/
+ http://containrrr.github.io/watchtower/linked-containers/
2019-06-01
daily
- http://localhost:8000/remote-hosts/
+ http://containrrr.github.io/watchtower/remote-hosts/
2019-06-01
daily
- http://localhost:8000/secure-connections/
+ http://containrrr.github.io/watchtower/secure-connections/
2019-06-01
daily
- http://localhost:8000/stop-signals/
+ http://containrrr.github.io/watchtower/stop-signals/
2019-06-01
daily
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 2a384c8..efb3367 100644
Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ
diff --git a/stop-signals/index.html b/stop-signals/index.html
index 9ae8245..3892136 100644
--- a/stop-signals/index.html
+++ b/stop-signals/index.html
@@ -1,4 +1,4 @@
-Stop signals - Watchtower Stop signals
When watchtower detects that a running container needs to be updated it will stop the container by sending it a SIGTERM signal.
+
Stop signals - Watchtower Stop signals
When watchtower detects that a running container needs to be updated it will stop the container by sending it a SIGTERM signal.
If your container should be shutdown with a different signal you can communicate this to watchtower by setting a label named com.centurylinklabs.watchtower.stop-signal with the value of the desired signal.
This label can be coded directly into your image by using the LABEL instruction in your Dockerfile:
LABEL com.centurylinklabs.watchtower.stop-signal="SIGHUP"
diff --git a/usage-overview/index.html b/usage-overview/index.html
index 9f8a171..c6fb980 100644
--- a/usage-overview/index.html
+++ b/usage-overview/index.html
@@ -1,4 +1,4 @@
-Usage overview - Watchtower Usage overview
Watchtower is itself packaged as a Docker container so installation is as simple as pulling the containrrr/watchtower image. If you are using ARM based architecture, pull the appropriate containrrr/watchtower:armhf-<tag> image from the containrrr Docker Hub.
+Usage overview - Watchtower Usage overview
Watchtower is itself packaged as a Docker container so installation is as simple as pulling the containrrr/watchtower image. If you are using ARM based architecture, pull the appropriate containrrr/watchtower:armhf-<tag> image from the containrrr Docker Hub.
Since the watchtower code needs to interact with the Docker API in order to monitor the running containers, you need to mount /var/run/docker.sock into the container with the -v flag when you run it.
Run the watchtower container with the following command:
docker run -d \