Difference between revisions of "External bind mounts"

From CRIU
Jump to: navigation, search
(External mounts, external/internal sharing/slavery.)
(don't make "Sharing" the subsection of "old days"; minor English fixes)
Line 68: Line 68:
 
  criu dump ... --external 'mnt[]'
 
  criu dump ... --external 'mnt[]'
  
Auto detect and dump all external bind mounts.
+
Auto-detect and dump all external bind mounts.
  
 
  criu dump ... --external 'mnt[]:s'
 
  criu dump ... --external 'mnt[]:s'
  
Auto detect and dump all external bind mounts, including the shared ones.
+
Auto-detect and dump all external bind mounts, including the shared ones.
  
 
  criu dump ... --external 'mnt[]:sm'
 
  criu dump ... --external 'mnt[]:sm'
  
Auto detect and dump all external bind mounts, including the shared and the master ones.
+
Auto-detect and dump all external bind mounts, including the shared and the master ones.
  
== Old days ==
+
== Sharing ==
 
 
For now the same behavior is configured with the <code>--ext-mount-map KEY:VAL</code> option. Soon this option will be [[deprecation|deprecated]].
 
 
 
[[Category:HOWTO]]
 
[[Category:External]]
 
 
 
=== Sharing for external bindmounts ===
 
  
 
External bindmounts can both have internal/external sharing. Please see the example:
 
External bindmounts can both have internal/external sharing. Please see the example:
Line 133: Line 126:
 
  # 899 843 0:5 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
 
  # 899 843 0:5 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw
  
Mounts 812 (on host) and 861 (in container) have the same sharing (shared group) - external sharing and mount 898 has it's own local shared group - internal sharing.
+
Mounts 812 (on the host) and 861 (in a container) have the same sharing (shared group) - external sharing and mount 898 has it's own local shared group - internal sharing.
 +
 
 +
Before [https://github.com/checkpoint-restore/criu/pull/906 #906] we were detecting this external/internal sharing state for auto-detected external mounts only, but we need it for manual external mounts too. Moreover, this also applies to manual external slave mounts they can be external/internal slaves too.
 +
 
 +
So we detect that the mount is from external sharing if in mount namespace of CRIU there are mounts of the same shared group and also we detect that the mount is from external slavery if there is no master mount for it in CT mount namespaces.
  
Before [https://github.com/checkpoint-restore/criu/pull/906 #906] we were detecting this external/internal sharing state for auto detected external mounts only, but we need it for manual external mounts too. Moreover this also applies to manual external slave mounts they can be external/internal slaves too.
+
== Old days ==
  
So we detect that the mount is from external sharing if in mount namespace of CRIU there are mounts of same shared group and also we detect that the mount is from external slavery if there is no master mount for it in CT mount namespaces.
+
For now the same behavior is configured with the <code>--ext-mount-map KEY:VAL</code> option. Soon this option will be [[deprecation|deprecated]].
 +
 
 +
[[Category:HOWTO]]
 +
[[Category:External]]

Revision as of 19:55, 25 March 2020

One of typical external resources when dumping a container (especially LXC/Docker) is a mount point whose root sits outside of the container's root. This situation was intended to be resolved using plugins but turned out to be common enough to introduce a built-in way of handling it.

What is external bind mount

The way to create such is simple as

mkdir /root
mount --bind /foo /root/bar
chroot /root

This is it. From now on, the /bar file is a mountpoint whose root (the source) is not accessible directly.

If you look at the /proc/$pid/mountinfo file of a task seeing such you would see smth like

11 23 8:3 /root / ... - ext4 /dev/sda1 ...
23 34 8:3 /foo /bar ... - ext4 /dev/sda1 ...

The columns 4 and 5 are root and mountpoint respectively. You can see, that the / is /root file from /dev/sda1 device and /bar file is a mountpoint with the root being /foo file from the same device.

How to teach CRIU to dump them

By default CRIU doesn't dump such mountpoints, because there's no way CRIU will be able to restore it -- the root of these mounts is out of scope of what CRIU dumped. In the logs you would see a message like

34:/bar doesn't have a proper root mount

which means the mountpoint /bar has inaccessible root.

To dump and restore them there's the --external mnt[KEY]:VAL option that sets up external mounts root mapping.

On dump, KEY is a mountpoint inside container, and corresponding VAL is a string that will be written into the image as mountpoint's root value.

On restore, KEY is the value from the image (VAL from dump), and the VAL is the path on host that will be bind-mounted into container (to the mountpoint path from image).

For example, if we want to dump the task above we should call

criu dump ... --external mnt[/bar]:barmount

The word barmount is an arbitrary identifier, that will be put in the image file instead of the original root path

criu show -f mountpoints.img -F mnt_id,root,mountpoint
mnt_id: 0x22 root: barmount mountpoint: /bar

On restore we should tell CRIU where to bind mount the barmount from like this

criu restore ... --external mnt[barmount]:/foo

With this CRIU will bind mount the /foo into proper mountpoint.

Auto detection

In case one wants CRIU to autodetect and dump all the external bind mounts, and there is no need to change host mount points on restore, one can use a special syntax:

criu dump ... --external mnt[]:flags

Note here is nothing inside square brackets, and the optional :flags argument can contain the following characters:

m
Also enable dumping of external master mounts (as in mount --make-slave)
s
Also enable dumping of external shared mounts (as in mount --make-shared)

By default, neither master nor shared external mounts are not dumped (if found, dump is aborted). Note if flags are not given, semicolon is optional.

Examples

criu dump ... --external 'mnt[]'

Auto-detect and dump all external bind mounts.

criu dump ... --external 'mnt[]:s'

Auto-detect and dump all external bind mounts, including the shared ones.

criu dump ... --external 'mnt[]:sm'

Auto-detect and dump all external bind mounts, including the shared and the master ones.

Sharing

External bindmounts can both have internal/external sharing. Please see the example:

# Preparation
unshare -m --propagation private
mkdir /external_mount_sharing_test
mount -t tmpfs tmpfs /external_mount_sharing_test/
mount --make-private /external_mount_sharing_test/
cd /external_mount_sharing_test
# Source of external mount
mkdir external_mount
mount -t tmpfs tmpfs-external external_mount/
mount --make-shared external_mount/
cat /proc/$$/mountinfo | grep external
# 811 755 0:60 / /external_mount_sharing_test rw,relatime - tmpfs tmpfs rw
# 812 811 0:62 / /external_mount_sharing_test/external_mount rw,relatime shared:290 - tmpfs tmpfs-external rw

# Switch to CT mntns
unshare -m --propagation unchanged sh
mkdir root
mount -t tmpfs tmpfs-root root/
mkdir root/external_sharing root/internal_sharing root/proc

# Create external mount
mount --bind external_mount/ root/external_sharing
mount --bind external_mount/ root/internal_sharing
mount --make-private root/internal_sharing
mount --make-shared root/internal_sharing

# More preparations
mount --bind /proc root/proc
cd root
mkdir bin lib64
SH=$(which sh)
cp $SH bin
cp $(ldd $SH | grep "/lib64" | sed 's/^.*\(\/lib64\S*\)\s.*$/\1/') lib64
CAT=$(which cat)
cp $CAT bin
cp $(ldd $CAT | grep "/lib64" | sed 's/^.*\(\/lib64\S*\)\s.*$/\1/') lib64
PATH=$PATH:/bin
chroot . sh
cat /proc/$$/mountinfo
# 843 841 0:63 / / rw,relatime - tmpfs tmpfs-root rw
# 861 843 0:62 / /external_sharing rw,relatime shared:290 - tmpfs tmpfs-external rw
# 898 843 0:62 / /internal_sharing rw,relatime shared:349 - tmpfs tmpfs-external rw
# 899 843 0:5 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw

Mounts 812 (on the host) and 861 (in a container) have the same sharing (shared group) - external sharing and mount 898 has it's own local shared group - internal sharing.

Before #906 we were detecting this external/internal sharing state for auto-detected external mounts only, but we need it for manual external mounts too. Moreover, this also applies to manual external slave mounts they can be external/internal slaves too.

So we detect that the mount is from external sharing if in mount namespace of CRIU there are mounts of the same shared group and also we detect that the mount is from external slavery if there is no master mount for it in CT mount namespaces.

Old days

For now the same behavior is configured with the --ext-mount-map KEY:VAL option. Soon this option will be deprecated.