From 8beb28d4f8a1e55e1589dfd6d7ba8bf365aacde6 Mon Sep 17 00:00:00 2001 From: Frederik Ring Date: Sun, 26 May 2024 10:28:46 +0200 Subject: [PATCH] Documentation should mention label visibility restrictions --- docs/how-tos/run-custom-commands.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/how-tos/run-custom-commands.md b/docs/how-tos/run-custom-commands.md index be4583d..b62e890 100644 --- a/docs/how-tos/run-custom-commands.md +++ b/docs/how-tos/run-custom-commands.md @@ -9,6 +9,11 @@ parent: How Tos In certain scenarios it can be required to run specific commands before and after a backup is taken (e.g. dumping a database). When mounting the Docker socket into the `docker-volume-backup` container, you can define pre- and post-commands that will be run in the context of the target container (it is also possible to run commands inside the `docker-volume-backup` container itself using this feature). + +{: .important } +In a multi-node Swarm setup, commands can currently only be run on the node the `offen/docker-volume-backup` container is running on. +Labeled containers on other nodes are not visible to the backup command. + Such commands are defined by specifying the command in a `docker-volume-backup.[step]-[pre|post]` label where `step` can be any of the following phases of a backup lifecycle: - `archive` (the tar archive is created)