c6090c290e
New functionality in hack/man-page-checker: start cross- referencing the man page 'Synopsis' line against the output of 'podman foo --help'. This is part 1, flag/option consistency. Part 2 (arg consistency) is too big and will have to wait for later. flag/option consistency means: if 'podman foo --help' includes the string '[flags]' in the Usage message, make sure the man page includes '[*options*]' in its Synopsis line, and vice-versa. This found several inconsistencies, which I've fixed. While doing this I realized that Cobra automatically includes a 'Flags:' subsection in its --help output for all subcommands that have defined flags. This is great - it lets us cross-check against the usage synopsis, and make sure that '[flags]' is present or absent as needed, without fear of human screwups. If a flag-less subcommand ever gets extended with flags, but the developer forgets to add '[flags]' and remove DisableFlagsInUseLine, we now have a test that will catch that. (This, too, caught two instances which I fixed). I don't actually know if the new man-page-checker functionality will work in CI: I vaguely recall that it might run before 'make podman' does; and also vaguely recall that some steps were taken to remedy that. Signed-off-by: Ed Santiago <santiago@redhat.com>
1.5 KiB
% podman-system-migrate(1)
NAME
podman-system-migrate - Migrate existing containers to a new podman version
SYNOPSIS
podman system migrate [options]
DESCRIPTION
podman system migrate migrates containers to the latest podman version.
podman system migrate takes care of migrating existing containers to the latest version of podman if any change is necessary.
"Rootless Podman uses a pause process to keep the unprivileged
namespaces alive. This prevents any change to the /etc/subuid and
/etc/subgid files from being propagated to the rootless containers
while the pause process is running.
For these changes to be propagated, it is necessary to first stop all
running containers associated with the user and to also stop the pause
process and delete its pid file. Instead of doing it manually, podman system migrate can be used to stop both the running containers and the
pause process. The /etc/subuid and /etc/subgid files can then be
edited or changed with usermod to recreate the user namespace with the
newly configured mappings.
OPTIONS
--new-runtime=runtime
Set a new OCI runtime for all containers. This can be used after a system upgrade which changes the default OCI runtime to move all containers to the new runtime. There are no guarantees that the containers will continue to work under the new runtime, as some runtimes support differing options and configurations.
SEE ALSO
podman(1), libpod.conf(5), usermod(8)
HISTORY
April 2019, Originally compiled by Giuseppe Scrivano (gscrivan at redhat dot com)