Fix links

This commit is contained in:
invis-z 2025-02-04 12:54:57 +08:00 committed by Jan O. Rundshagen
parent e07234a379
commit c571dc4b6a
2 changed files with 5 additions and 5 deletions

View file

@ -245,7 +245,7 @@ Environment Variable: WATCHTOWER_DISABLE_CONTAINERS
## Without updating containers ## Without updating containers
Will only monitor for new images, send notifications and invoke Will only monitor for new images, send notifications and invoke
the [pre-check/post-check hooks](https://watchtower.devcdn.nelifecycle-hooks/), but will __not__ update the the [pre-check/post-check hooks](https://watchtower.devcdn.net/lifecycle-hooks/), but will __not__ update the
containers. containers.
!!! note !!! note
@ -325,7 +325,7 @@ Environment Variable: WATCHTOWER_RUN_ONCE
## HTTP API Mode ## HTTP API Mode
Runs Watchtower in HTTP API mode, only allowing image updates to be triggered by an HTTP request. Runs Watchtower in HTTP API mode, only allowing image updates to be triggered by an HTTP request.
For details see [HTTP API](https://watchtower.devcdn.nehttp-api-mode). For details see [HTTP API](https://watchtower.devcdn.net/http-api-mode).
```text ```text
Argument: --http-api-update Argument: --http-api-update
@ -357,7 +357,7 @@ Environment Variable: WATCHTOWER_HTTP_API_PERIODIC_POLLS
## Filter by scope ## Filter by scope
Update containers that have a `com.centurylinklabs.watchtower.scope` label set with the same value as the given argument. Update containers that have a `com.centurylinklabs.watchtower.scope` label set with the same value as the given argument.
This enables [running multiple instances](https://watchtower.devcdn.nerunning-multiple-instances). This enables [running multiple instances](https://watchtower.devcdn.net/running-multiple-instances).
!!! note "Filter by lack of scope" !!! note "Filter by lack of scope"
If you want other instances of watchtower to ignore the scoped containers, set this argument to `none`. If you want other instances of watchtower to ignore the scoped containers, set this argument to `none`.

View file

@ -3,7 +3,7 @@ By default, watchtower will watch all containers. However, sometimes only some c
There are two options: There are two options:
- **Fully exclude**: You can choose to exclude containers entirely from being watched by watchtower. - **Fully exclude**: You can choose to exclude containers entirely from being watched by watchtower.
- **Monitor only**: In this mode, watchtower checks for container updates, sends notifications and invokes the [pre-check/post-check hooks](https://watchtower.devcdn.nelifecycle-hooks/) on the containers but does **not** perform the update. - **Monitor only**: In this mode, watchtower checks for container updates, sends notifications and invokes the [pre-check/post-check hooks](https://watchtower.devcdn.net/lifecycle-hooks/) on the containers but does **not** perform the update.
## Full Exclude ## Full Exclude
@ -78,4 +78,4 @@ Or, it can be specified as part of the `docker run` command line:
docker run -d --label=com.centurylinklabs.watchtower.monitor-only=true someimage docker run -d --label=com.centurylinklabs.watchtower.monitor-only=true someimage
``` ```
When the label is specified on a container, watchtower treats that container exactly as if [`WATCHTOWER_MONITOR_ONLY`](https://watchtower.devcdn.nearguments/#without_updating_containers) was set, but the effect is limited to the individual container. When the label is specified on a container, watchtower treats that container exactly as if [`WATCHTOWER_MONITOR_ONLY`](https://watchtower.devcdn.net/arguments/#without_updating_containers) was set, but the effect is limited to the individual container.