Skip to content

Commit 1d1ca72

Browse files
committed
Enhanced the docker image update section.
1 parent 218852f commit 1d1ca72

File tree

1 file changed

+17
-3
lines changed

1 file changed

+17
-3
lines changed

README.md

Lines changed: 17 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -162,8 +162,19 @@ services:
162162
163163
## Docker Image Update
164164
165-
If the system on which the container runs doesn't provide a way to easily update
166-
the Docker image, the following steps can be followed:
165+
Because features are added, issues are fixed, or simply because a new version
166+
of the containerized application is integrated, the Docker image is regularly
167+
updated. Different methods can be used to update the Docker image.
168+
169+
The system used to run the container may have a built-in way to update
170+
containers. If so, this could be your primary way to update Docker images.
171+
172+
An other way is to have the image be automatically updated with [Watchtower].
173+
Whatchtower is a container-based solution for automating Docker image updates.
174+
This is a "set and forget" type of solution: once a new image is available,
175+
Watchtower will seamlessly perform the necessary steps to update the container.
176+
177+
Finally, the Docker image can be manually updated with these steps:
167178
168179
1. Fetch the latest image:
169180
```
@@ -177,7 +188,10 @@ docker stop nginx-proxy-manager
177188
```
178189
docker rm nginx-proxy-manager
179190
```
180-
4. Start the container using the `docker run` command.
191+
4. Create and start the container using the `docker run` command, with the
192+
the same parameters that were used when it was deployed initially.
193+
194+
[Watchtower]: https://github.com/containrrr/watchtower
181195

182196
### Synology
183197

0 commit comments

Comments
 (0)