Difference between revisions of "Bind mounts"
m (Reverted edits by StevenCook (talk) to last revision by Kir) |
(fix the mount script creation process!) |
||
| Line 5: | Line 5: | ||
CTID=777 | CTID=777 | ||
| − | + | echo '#!/bin/bash | |
| − | #!/bin/bash | ||
. /etc/vz/vz.conf | . /etc/vz/vz.conf | ||
. ${VE_CONFFILE} | . ${VE_CONFFILE} | ||
| Line 13: | Line 12: | ||
if [ ! -e ${VE_ROOT}${DST} ]; then mkdir -p ${VE_ROOT}${DST}; fi | 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} | ||
| − | + | ' > /etc/vz/conf/${CTID}.mount | |
chmod +x /etc/vz/conf/${CTID}.mount | chmod +x /etc/vz/conf/${CTID}.mount | ||
Revision as of 01:13, 20 March 2014
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
echo '#!/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}
' > /etc/vz/conf/${CTID}.mount
chmod +x /etc/vz/conf/${CTID}.mountIf 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
