1ATOMIC(1) June 2015 ATOMIC(1)
2
3
4
6 atomic-mount - Mount Images/Containers to Filesystem
7
8
9
11 atomic mount [--live | --shared | --storage=[ostree|docker] |
12 [-o|--options OPTIONS]] [REGISTRY/]REPO[:TAG]|UUID|NAME DIRECTORY
13
14
15
17 atomic mount attempts to mount the underlying filesystem of a container
18 or image into the host filesystem. Accepts one of image UUID, container
19 UUID, container NAME, or image REPO (optionally with registry and tag
20 information). If the given UUID or NAME is a container, and --live is
21 not set, then atomic mount will create a snapshot of the container by
22 committing it to a temporary image and spawning a temporary container
23 from that image. If UUID or REPO refers to an image, then atomic mount
24 will simply create a temporary container from the given image. If the
25 UID is not zero, i.e. not being run as root, then atomic mount will
26 call ostree checkout with --user-mode option. It will also ignore the
27 mount system call, since ostree checkout takes care of that. All
28 temporary artifacts are cleaned upon atomic unmount. Atomic mount is
29 only supported on the devicemapper and overlayfs docker storage
30 backends. If an image stored on an OSTree repository is mounted, then
31 a temporary checkout is done, which will be deleted by atomic unmount.
32
33
34
36 -o|--options OPTIONS Specify options to be passed to mount. All options
37 accepted by the 'mount' command are valid. The default mount options
38 for the devicemapper backend (if the --live flag is unset) are:
39 'ro,nodev,nosuid'. If the -o flag is specified, then no default options
40 are assumed. Use of the 'rw' flag is discouraged, as writes into the
41 atomic temporary containers are never preserved. Use of this option
42 conflicts with --live, as live containers have predetermined, immutable
43 mount options. The OverlayFS driver has, by default, only the 'ro'
44 option set, and the 'rw' option is illegal and will cause the program
45 to terminate.
46
47
48 --live Mount a running container live, writable, and synchronized. This
49 option allows the user to modify the container's contents as the
50 container runs or update the container's software without rebuilding
51 the container. If live mode is used, no mount options may be provided.
52 Live mode is not supported on the OverlayFS docker storage driver.
53
54
55 --shared Mount a container image with a shared SELinux label
56
57
58 [--storage=[ostree|docker]] Optionally specify the storage of the
59 image. Will prompt user to specify if the same image name exists in
60 both ostree and docker, and the user did not specify.
61
62
63
65 June 2015, Originally compiled by William Temple (wtemple at redhat dot
66 com)
67
68
69
70Will Temple Atomic Man Pages ATOMIC(1)