Merge pull request #6858 from vrothberg/fix-6793

auto-update: clarify systemd-unit requirements
This commit is contained in:
OpenShift Merge Robot
2020-07-06 09:28:08 -04:00
committed by GitHub
2 changed files with 5 additions and 0 deletions

View File

@ -16,6 +16,8 @@ var (
autoUpdateDescription = `Auto update containers according to their auto-update policy. autoUpdateDescription = `Auto update containers according to their auto-update policy.
Auto-update policies are specified with the "io.containers.autoupdate" label. 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.` Note that this command is experimental. Please refer to the podman-auto-update(1) man page for details.`
autoUpdateCommand = &cobra.Command{ autoUpdateCommand = &cobra.Command{
Use: "auto-update [flags]", Use: "auto-update [flags]",

View File

@ -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. 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. 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 ## OPTIONS
**--authfile**=*path* **--authfile**=*path*