summaryrefslogtreecommitdiff
path: root/docs/podman-system-migrate.1.md
Commit message (Collapse)AuthorAge
* Migrate can move containers to a new runtimeMatthew Heon2019-10-10
| | | | | | | | | | | | This is a horrible hack to work around issues with Fedora 31, but other distros might need it to, so we'll move it upstream. I do not recommend this functionality for general use, and the manpages and other documentation will reflect this. But for some upgrade cases, it will be the only thing that allows for a working system. Signed-off-by: Matthew Heon <matthew.heon@pm.me>
* Fix formatting and enable hack/man-page-checkerRyan Whalen2019-08-30
| | | | Signed-off-by: Ryan Whalen <rj.whalen@gmail.com>
* docs: add note to system migrateGiuseppe Scrivano2019-06-19
| | | | | | | add a note explaining how it can be used to recreate the rootless user namespace. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
* standardize documentation formattingAshley Cui2019-06-10
| | | | Signed-off-by: Ashley Cui <ashleycui16@gmail.com>
* system: add new subcommand "migrate"Giuseppe Scrivano2019-04-26
it is useful to migrate existing containers to a new version of podman. Currently, it is needed to migrate rootless containers that were created with podman <= 1.2 to a newer version which requires all containers to be running in the same user namespace. Closes: https://github.com/containers/libpod/issues/2935 Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>