Difference between revisions of "Bind mounts"
(Change note on mounting inside containers, add note on cross-container mounts) |
YuKobayashi (talk | contribs) |
||
Line 10: | Line 10: | ||
SRC=/mnt/disk | SRC=/mnt/disk | ||
DST=/mnt/disk | DST=/mnt/disk | ||
+ | if [ ! -e ${VE_ROOT}${DST} ]; then mkdir -p ${VE_ROOT}${DST}; fi | ||
mount -n -t simfs ${SRC} ${VE_ROOT}${DST} -o ${SRC} | mount -n -t simfs ${SRC} ${VE_ROOT}${DST} -o ${SRC} | ||
EOF | EOF |
Revision as of 10:05, 13 February 2012
Bind mounts can be used to make directories on the hardware node visible to the container.
This is how you can make host system's /mnt/disk
directory available to a container 777:
CTID=777
cat << EOF > /etc/vz/conf/${CTID}.mount
#!/bin/bash
. /etc/vz/vz.conf
. ${VE_CONFFILE}
SRC=/mnt/disk
DST=/mnt/disk
if [ ! -e ${VE_ROOT}${DST} ]; then mkdir -p ${VE_ROOT}${DST}; fi
mount -n -t simfs ${SRC} ${VE_ROOT}${DST} -o ${SRC}
EOF
chmod +x /etc/vz/conf/${CTID}.mount
If you want read-only mount, add -r
option to mount command.
Note: When specifying destination directory, always use /vz/root/ or ${VE_ROOT} env. variable (avoid using /vz/private) |
Note: When binding directories from one container to another, make sure you have proper boot order (See BOOTORDER param.) |
See also
- vzctl(8) (ACTION SCRIPTS section)
- NFS
- FUSE
- Mounting filesystems