2015-10-28 16:24:13 -04:00
|
|
|
% ATOMIC(1) Atomic Man Pages
|
|
|
|
|
% Shishir Mahajan
|
|
|
|
|
% October 2015
|
|
|
|
|
# NAME
|
2016-05-03 14:30:08 -04:00
|
|
|
atomic-storage - Manage container storage.
|
2015-10-28 16:24:13 -04:00
|
|
|
|
|
|
|
|
# SYNOPSIS
|
2016-05-03 14:30:08 -04:00
|
|
|
**atomic storage COMMAND [OPTIONS]**
|
2015-10-28 16:24:13 -04:00
|
|
|
|
2017-02-27 16:26:48 -05:00
|
|
|
atomic storage allows the user to easily manage container storage.
|
2016-06-14 06:00:56 -04:00
|
|
|
You can reset your container environment back to its initial state as well
|
2016-05-03 14:30:08 -04:00
|
|
|
as migrate all images, volumes, and containers from one version of atomic
|
|
|
|
|
to another. With this command, users can quickly save all their data from
|
|
|
|
|
the current atomic instance, change the container's content storage backend,
|
|
|
|
|
and then import all their old data to the new system.
|
2015-10-28 16:24:13 -04:00
|
|
|
|
|
|
|
|
# COMMANDS
|
|
|
|
|
**export**
|
|
|
|
|
|
|
|
|
|
export command will export all the current images, volumes, and containers
|
2016-05-16 12:07:03 -04:00
|
|
|
to the specified directory (/var/lib/atomic/migrate by default), in the /images,
|
2015-11-01 12:53:18 -05:00
|
|
|
/volumes, /containers subdirectories.
|
2015-10-28 16:24:13 -04:00
|
|
|
|
|
|
|
|
**import**
|
|
|
|
|
|
2016-05-16 12:07:03 -04:00
|
|
|
import command will import images, volumes, and containers from the specified
|
2015-11-01 12:53:18 -05:00
|
|
|
directory (/var/lib/atomic/migrate by default) into the new atomic instance.
|
2015-10-28 16:24:13 -04:00
|
|
|
|
2016-05-03 14:30:08 -04:00
|
|
|
**reset**
|
|
|
|
|
Remove all containers/images from your system
|
|
|
|
|
|
2016-05-16 12:07:03 -04:00
|
|
|
**modify**
|
|
|
|
|
Modify the default storage setup
|
|
|
|
|
|
2015-10-28 16:24:13 -04:00
|
|
|
# export OPTIONS
|
|
|
|
|
**-h** **--help**
|
|
|
|
|
Print usage statement
|
|
|
|
|
|
|
|
|
|
**--graph**
|
2016-05-16 12:07:03 -04:00
|
|
|
Root of the docker runtime. If you are running docker at the default
|
|
|
|
|
location (/var/lib/docker), you don't need to pass this flag. However
|
2015-10-28 16:24:13 -04:00
|
|
|
if you are running docker at a custom location. This flag must be set.
|
|
|
|
|
|
|
|
|
|
**--dir**
|
2016-05-16 12:07:03 -04:00
|
|
|
Directory in which to temporarily store the files (can be an existing
|
2015-10-28 16:24:13 -04:00
|
|
|
directory, or the command will create one). If no directory is specified,
|
2015-11-01 12:53:18 -05:00
|
|
|
/var/lib/atomic/migrate would be used as default.
|
2015-10-28 16:24:13 -04:00
|
|
|
|
2016-09-09 08:52:48 -04:00
|
|
|
# Note:
|
|
|
|
|
Atomic --assumeyes option can be used
|
|
|
|
|
|
|
|
|
|
[**-y|--assumeyes**]
|
|
|
|
|
Delete image(s) without conformation from the user
|
2016-05-03 14:30:08 -04:00
|
|
|
|
2015-10-28 16:24:13 -04:00
|
|
|
# import OPTIONS
|
|
|
|
|
**-h** **--help**
|
|
|
|
|
Print usage statement
|
|
|
|
|
|
|
|
|
|
**--graph**
|
|
|
|
|
Root of the docker runtime. If you are running docker at the default
|
|
|
|
|
location (/var/lib/docker), you don't need to pass this flag. However
|
|
|
|
|
if you are running docker at a custom location. This flag must be set.
|
|
|
|
|
|
|
|
|
|
**--dir**
|
2016-05-16 12:07:03 -04:00
|
|
|
Directory from which to import the files (images, containers and volumes).
|
|
|
|
|
If this flag is not set atomic storage will assume the import location to
|
|
|
|
|
be /var/lib/atomic/migrate. Whether you set this flag or use the default,
|
2015-10-28 16:24:13 -04:00
|
|
|
the directory must be present for the import to happen successfully.
|
|
|
|
|
|
2016-05-16 12:07:03 -04:00
|
|
|
# modify OPTIONS
|
|
|
|
|
**-h** **--help**
|
|
|
|
|
Print usage statement
|
|
|
|
|
|
|
|
|
|
**--add-device**
|
2017-03-13 11:54:08 -04:00
|
|
|
Add block devices to storage pool. This command will expand your devicemapper
|
2016-05-16 12:07:03 -04:00
|
|
|
storage pool by adding the block device. Only works with devicemapper driver.
|
|
|
|
|
|
2017-03-13 11:54:08 -04:00
|
|
|
E.g atomic storage modify --add-device /dev/vdb will add /dev/vdb
|
|
|
|
|
to storage pool.
|
2017-02-27 16:26:48 -05:00
|
|
|
|
2016-06-10 13:11:09 +03:00
|
|
|
**--remove-device**
|
|
|
|
|
Remove block devices from the storage pool. If a device is not empty, this
|
|
|
|
|
command will try to first move its data to some other device in the pool.
|
|
|
|
|
|
|
|
|
|
**--remove-unused-devices**
|
|
|
|
|
Remove all block devices from the storage pool that are currently unused.
|
|
|
|
|
|
2016-05-16 12:07:03 -04:00
|
|
|
**--driver**
|
2017-03-13 11:54:08 -04:00
|
|
|
Backend storage driver for containers. This options the storage driver.
|
|
|
|
|
Drivers supported: devicemapper, overlay, overlay2
|
2016-05-16 12:07:03 -04:00
|
|
|
|
2017-02-06 15:35:39 -05:00
|
|
|
**--lvname**
|
2017-03-13 11:54:08 -04:00
|
|
|
Logical volume name for container storage.
|
2017-02-27 16:26:48 -05:00
|
|
|
E.g atomic storage modify --lvname="container-root-lv"
|
2017-03-13 11:54:08 -04:00
|
|
|
--rootfs="/var/lib/containers" will create logical volume named
|
|
|
|
|
container-root-lv and mount it on /var/lib/containers.
|
2017-02-06 15:35:39 -05:00
|
|
|
Note: You must set --rootfs when setting --lvname.
|
|
|
|
|
|
|
|
|
|
**--rootfs**
|
2017-03-13 11:54:08 -04:00
|
|
|
Mountpath where logical volume for container storage would be mounted.
|
2017-02-27 16:26:48 -05:00
|
|
|
E.g. atomic storage modify --rootfs="/var/lib/containers"
|
2017-03-13 11:54:08 -04:00
|
|
|
--lvname="container-root-lv" will create logical volume named
|
|
|
|
|
container-root-lv and mount it on /var/lib/containers.
|
2017-02-06 15:35:39 -05:00
|
|
|
Note: You must set --lvname when setting --rootfs.
|
|
|
|
|
|
2017-02-16 14:31:35 -05:00
|
|
|
**--lvsize**
|
2017-03-13 11:54:08 -04:00
|
|
|
Logical volume size for container storage. It defaults to 40% of all free space.
|
2017-02-27 16:26:48 -05:00
|
|
|
--lvsize can take values acceptable to "lvcreate -L" as well as some values
|
|
|
|
|
acceptable to "lvcreate -l". If user intends to pass values acceptable to
|
|
|
|
|
"lvcreate -l", then only those values which contains "%" in syntax are acceptable.
|
|
|
|
|
If value does not contain "%" it is assumed value is suitable for "lvcreate -L".
|
|
|
|
|
E.g. atomic storage modify --rootfs="/var/lib/containers" --lvname="container-root-lv"
|
2017-03-13 11:54:08 -04:00
|
|
|
--lvsize=20%FREE will create logical volume named container-root-lv of size
|
|
|
|
|
(20% of the available free space in the volume group)
|
|
|
|
|
and mount it on /var/lib/containers.
|
2017-02-16 14:31:35 -05:00
|
|
|
Note: You must set --lvname and --rootfs when setting --lvsize.
|
|
|
|
|
|
2016-08-05 19:46:24 +03:00
|
|
|
**--vgroup**
|
2017-03-13 11:54:08 -04:00
|
|
|
The name of the volume group for the storage pool.
|
2016-08-05 19:46:24 +03:00
|
|
|
|
2016-11-03 16:01:52 -04:00
|
|
|
# reset OPTIONS
|
|
|
|
|
**-h** **--help**
|
|
|
|
|
Print usage statement
|
|
|
|
|
|
|
|
|
|
**--graph**
|
2017-02-27 16:26:48 -05:00
|
|
|
Root of the container runtime. atomic will search for either /var/lib/docker or
|
|
|
|
|
/var/lib/docker-latest, if only one exists, atomic will select it as the default.
|
|
|
|
|
If both exists or you are running docker with a graph storage at a non default
|
|
|
|
|
location, you need to pass this flag.
|
2016-11-03 16:01:52 -04:00
|
|
|
|
2015-10-28 16:24:13 -04:00
|
|
|
# HISTORY
|
|
|
|
|
October 2015, Originally compiled by Shishir Mahajan (shishir dot mahajan at redhat dot com)
|