77 lines
2.8 KiB
Groff
77 lines
2.8 KiB
Groff
.nh
|
|
.TH podman-system-reset 1
|
|
.SH NAME
|
|
podman-system-reset \- Reset storage back to initial state
|
|
|
|
.SH SYNOPSIS
|
|
\fBpodman system reset\fP [\fIoptions\fP]
|
|
|
|
.SH DESCRIPTION
|
|
\fBpodman system reset\fP removes all pods, containers, images, networks and volumes, and machines.
|
|
It also removes the configured graphRoot and runRoot directories. Make sure these are not set to
|
|
some important directory.
|
|
|
|
.PP
|
|
This command must be run \fBbefore\fP changing any of the following fields in the
|
|
\fBcontainers.conf\fR or \fBstorage.conf\fR files: \fBdriver\fR, \fBstatic_dir\fR, \fBtmp_dir\fR
|
|
or \fBvolume_path\fR\&.
|
|
|
|
.PP
|
|
\fBpodman system reset\fR reads the current configuration and attempts to remove all
|
|
of the relevant configurations. If the administrator modified the configuration files first,
|
|
\fBpodman system reset\fR might not be able to clean up the previous storage.
|
|
|
|
.PP
|
|
\fBpodman system reset\fR does not restart podman.service and podman.socket systemd units. You may need to manually restart it after running this command.
|
|
|
|
.SH OPTIONS
|
|
.SS \fB--force\fP, \fB-f\fP
|
|
Do not prompt for confirmation
|
|
|
|
.SS \fB--help\fP, \fB-h\fP
|
|
Print usage statement
|
|
|
|
.SH EXAMPLES
|
|
Reset all storage back to a clean initialized state.
|
|
|
|
.EX
|
|
$ podman system reset
|
|
WARNING! This will remove:
|
|
- all containers
|
|
- all pods
|
|
- all images
|
|
- all networks
|
|
- all build cache
|
|
- all machines
|
|
- all volumes
|
|
- the graphRoot directory: /var/lib/containers/storage
|
|
- the runRoot directory: /run/containers/storage
|
|
Are you sure you want to continue? [y/N] y
|
|
.EE
|
|
|
|
.PP
|
|
Force reset all storage back to a clean initialized state.
|
|
|
|
.EX
|
|
$ podman system reset --force
|
|
.EE
|
|
|
|
.SS Switching rootless user from VFS driver to overlay with fuse-overlayfs
|
|
If the user ran rootless containers without having the \fBfuse-overlayfs\fR program
|
|
installed, podman defaults to the \fBvfs\fR storage in their home directory. If they
|
|
want to switch to use fuse-overlay, they must install the fuse-overlayfs
|
|
package. The user needs to reset the storage to use overlayfs by default.
|
|
Execute \fBpodman system reset\fR as the user first to remove the VFS storage. Now
|
|
the user can edit the \fB/etc/containers/storage.conf\fR to make any changes if
|
|
necessary. If the system's default was already \fBoverlay\fR, then no changes are
|
|
necessary to switch to fuse-overlayfs. Podman looks for the existence of
|
|
fuse-overlayfs to use it when set in the \fBoverlay\fR driver, only falling back to vfs
|
|
if the program does not exist. Users can run \fBpodman info\fR to ensure Podman is
|
|
using fuse-overlayfs and the overlay driver.
|
|
|
|
.SH SEE ALSO
|
|
\fBpodman(1)\fP, \fBpodman-system(1)\fP, \fBfuse-overlayfs(1)\fP, \fBcontainers-storage.conf(5)\fP
|
|
|
|
.SH HISTORY
|
|
November 2019, Originally compiled by Dan Walsh (dwalsh at redhat dot com)
|