1ATOMIC(1)                        October 2015                        ATOMIC(1)
2
3
4

NAME

6       atomic-storage - Manage container storage.
7
8
9

SYNOPSIS

11       atomic storage COMMAND [OPTIONS]
12
13
14       atomic storage allows the user to easily manage container storage.  You
15       can reset your container environment back to its initial state as well
16       as migrate all images, volumes, and containers from one version of
17       atomic to another. With this command, users can quickly save all their
18       data from the current atomic instance, change the container's content
19       storage backend, and then import all their old data to the new system.
20
21
22

COMMANDS

24       export
25
26
27       export command will export all the current images, volumes, and
28       containers to the specified directory (/var/lib/atomic/migrate by
29       default), in the /images, /volumes, /containers subdirectories.
30
31
32       import
33
34
35       import command will import images, volumes, and containers from the
36       specified directory (/var/lib/atomic/migrate by default) into the new
37       atomic instance.
38
39
40       reset
41           Remove all containers/images from your system
42
43
44       modify
45           Modify the default storage setup
46
47
48

export OPTIONS

50       -h --help
51         Print usage statement
52
53
54       --graph Root of the docker runtime. If you are running docker at the
55       default location (/var/lib/docker), you don't need to pass this flag.
56       However if you are running docker at a custom location. This flag must
57       be set.
58
59
60       --dir Directory in which to temporarily store the files (can be an
61       existing directory, or the command will create one). If no directory is
62       specified, /var/lib/atomic/migrate would be used as default.
63
64
65

Note:

67       Atomic --assumeyes option can be used
68
69
70       [-y|--assumeyes]
71         Delete image(s) without conformation from the user
72
73
74

import OPTIONS

76       -h --help
77         Print usage statement
78
79
80       --graph Root of the docker runtime. If you are running docker at the
81       default location (/var/lib/docker), you don't need to pass this flag.
82       However if you are running docker at a custom location. This flag must
83       be set.
84
85
86       --dir Directory from which to import the files (images, containers and
87       volumes).  If this flag is not set atomic storage will assume the
88       import location to be /var/lib/atomic/migrate. Whether you set this
89       flag or use the default, the directory must be present for the import
90       to happen successfully.
91
92
93

modify OPTIONS

95       -h --help
96         Print usage statement
97
98
99       --add-device Add block devices to storage pool. This command will
100       expand your devicemapper storage pool by adding the block device. Only
101       works with devicemapper driver.
102
103
104       E.g atomic storage modify --add-device /dev/vdb will add /dev/vdb to
105       storage pool.
106
107
108       --remove-device Remove block devices from the storage pool.  If a
109       device is not empty, this command will try to first move its data to
110       some other device in the pool.
111
112
113       --remove-unused-devices Remove all block devices from the storage pool
114       that are currently unused.
115
116
117       --driver Backend storage driver for containers. This options the
118       storage driver.  Drivers supported: devicemapper, overlay, overlay2
119
120
121       --lvname Logical volume name for container storage.  E.g atomic storage
122       modify --lvname="container-root-lv" --rootfs="/var/lib/containers" will
123       create logical volume named container-root-lv and mount it on
124       /var/lib/containers.  Note: You must set --rootfs when setting
125       --lvname.
126
127
128       --rootfs Mountpath where logical volume for container storage would be
129       mounted.  E.g. atomic storage modify --rootfs="/var/lib/containers"
130       --lvname="container-root-lv" will create logical volume named
131       container-root-lv and mount it on /var/lib/containers.  Note: You must
132       set --lvname when setting --rootfs.
133
134
135       --lvsize Logical volume size for container storage. It defaults to 40%
136       of all free space.  --lvsize can take values acceptable to "lvcreate
137       -L" as well as some values acceptable to "lvcreate -l". If user intends
138       to pass values acceptable to "lvcreate -l", then only those values
139       which contains "%" in syntax are acceptable.  If value does not contain
140       "%" it is assumed value is suitable for "lvcreate -L".  E.g. atomic
141       storage modify --rootfs="/var/lib/containers"
142       --lvname="container-root-lv" --lvsize=20%FREE will create logical
143       volume named container-root-lv of size (20% of the available free space
144       in the volume group) and mount it on /var/lib/containers.  Note: You
145       must set --lvname and --rootfs when setting --lvsize.
146
147
148       --vgroup The name of the volume group for the storage pool.
149
150
151

reset OPTIONS

153       -h --help
154         Print usage statement
155
156
157       --graph Root of the container runtime. atomic will search for either
158       /var/lib/docker or /var/lib/docker-latest, if only one exists, atomic
159       will select it as the default.  If both exists or you are running
160       docker with a graph storage at a non default location, you need to pass
161       this flag.
162
163
164

HISTORY

166       October 2015, Originally compiled by Shishir Mahajan (shishir dot
167       mahajan at redhat dot com)
168
169
170
171Shishir Mahajan                 Atomic Man Pages                     ATOMIC(1)