atomic-mount (1) - Linux Man Pages

atomic-mount: Mount Images/Containers to Filesystem


atomic-mount - Mount Images/Containers to Filesystem


atomic mount [--live | --shared | --storage=[ostree|docker] | [-o|--options OPTIONS]] [REGISTRY/]REPO[:TAG]|UUID|NAME DIRECTORY


atomic mount attempts to mount the underlying filesystem of a container or image into the host filesystem. Accepts one of image UUID, container UUID, container NAME, or image REPO (optionally with registry and tag information). If the given UUID or NAME is a container, and --live is not set, then atomic mount will create a snapshot of the container by committing it to a temporary image and spawning a temporary container from that image. If UUID or REPO refers to an image, then atomic mount will simply create a temporary container from the given image. If the UID is not zero, i.e. not being run as root, then atomic mount will call ostree checkout with --user-mode option. It will also ignore the mount system call, since ostree checkout takes care of that. All temporary artifacts are cleaned upon atomic unmount. Atomic mount is only supported on the devicemapper and overlayfs docker storage backends. If an image stored on an OSTree repository is mounted, then a temporary checkout is done, which will be deleted by atomic unmount.


-o|--options OPTIONS Specify options to be passed to mount. All options accepted by the 'mount' command are valid. The default mount options for the devicemapper backend (if the --live flag is unset) are: 'ro,nodev,nosuid'. If the -o flag is specified, then no default options are assumed. Use of the 'rw' flag is discouraged, as writes into the atomic temporary containers are never preserved. Use of this option conflicts with --live, as live containers have predetermined, immutable mount options. The OverlayFS driver has, by default, only the 'ro' option set, and the 'rw' option is illegal and will cause the program to terminate.

--live Mount a running container live, writable, and synchronized. This option allows the user to modify the container's contents as the container runs or update the container's software without rebuilding the container. If live mode is used, no mount options may be provided. Live mode is not supported on the OverlayFS docker storage driver.

--shared Mount a container image with a shared SELinux label

[--storage=[ostree|docker]] Optionally specify the storage of the image. Will prompt user to specify if the same image name exists in both ostree and docker, and the user did not specify.


June 2015, Originally compiled by William Temple (wtemple at redhat dot com)