Difference between revisions of "Bind mounts"
(Note on using folders from another container) |
(Change note on mounting inside containers, add note on cross-container mounts) |
||
| Line 17: | Line 17: | ||
If you want read-only mount, add <code>-r</code> option to mount command. | If you want read-only mount, add <code>-r</code> option to mount command. | ||
| − | {{Note| | + | {{Note|When specifying destination directory, always use /vz/root/ or ${VE_ROOT} env. variable <nowiki>(avoid using /vz/private)</nowiki>}} |
| + | {{Note|When binding directories from one container to another, make sure you have proper boot order (See [[Man/vzctl.8|BOOTORDER]] param.)}} | ||
== See also == | == See also == | ||
Revision as of 13:17, 9 January 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
mount -n -t simfs ${SRC} ${VE_ROOT}${DST} -o ${SRC}
EOF
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
