summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2020-07-06 11:14:33 +0200
committerValentin Rothberg <rothberg@redhat.com>2020-07-06 11:14:33 +0200
commit0ef5def0beb7f7e5f12db7c9fba1d1b7bb45ce73 (patch)
tree9480de5ebecb65ac8a0caee3f5373348ab7b7044
parent41ccc045fb492e79d8b6c1bf2dba97b0fa912afa (diff)
downloadpodman-0ef5def0beb7f7e5f12db7c9fba1d1b7bb45ce73.tar.gz
podman-0ef5def0beb7f7e5f12db7c9fba1d1b7bb45ce73.tar.bz2
podman-0ef5def0beb7f7e5f12db7c9fba1d1b7bb45ce73.zip
auto-update: clarify systemd-unit requirements
Clarify in the help message and the man page that auto updates only work with systemd units that are similar to the ones from `generate systemd --new`. Units that merely start/stop a container do not work as they will use the same image. Fixes: #6793 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
-rw-r--r--cmd/podman/auto-update.go2
-rw-r--r--docs/source/markdown/podman-auto-update.1.md3
2 files changed, 5 insertions, 0 deletions
diff --git a/cmd/podman/auto-update.go b/cmd/podman/auto-update.go
index 11433bc25..eed211ff1 100644
--- a/cmd/podman/auto-update.go
+++ b/cmd/podman/auto-update.go
@@ -16,6 +16,8 @@ var (
autoUpdateDescription = `Auto update containers according to their auto-update policy.
Auto-update policies are specified with the "io.containers.autoupdate" label.
+ Containers are expected to run in systemd units created with "podman-generate-systemd --new",
+ or similar units that create new containers in order to run the updated images.
Note that this command is experimental. Please refer to the podman-auto-update(1) man page for details.`
autoUpdateCommand = &cobra.Command{
Use: "auto-update [flags]",
diff --git a/docs/source/markdown/podman-auto-update.1.md b/docs/source/markdown/podman-auto-update.1.md
index f37280cda..b6941362a 100644
--- a/docs/source/markdown/podman-auto-update.1.md
+++ b/docs/source/markdown/podman-auto-update.1.md
@@ -23,6 +23,9 @@ Note that `podman auto-update` relies on systemd and requires a fully-qualified
This enforcement is necessary to know which image to actually check and pull.
If an image ID was used, Podman would not know which image to check/pull anymore.
+Moreover, the systemd units are expected to be generated with `podman-generate-systemd --new`, or similar units that create new containers in order to run the updated images.
+Systemd units that start and stop a container cannot run a new image.
+
## OPTIONS
**--authfile**=*path*