pct: cleanup, use "mount point" instead of mountpoint

This commit is contained in:
Dietmar Maurer 2016-05-07 14:47:51 +02:00
parent fe154a4fa3
commit 9e44e493d8

View File

@ -324,14 +324,15 @@ mount local directories using bind mounts. That way you can access
local storage inside containers with zero overhead. Such bind mounts local storage inside containers with zero overhead. Such bind mounts
also provide an easy way to share data between different containers. also provide an easy way to share data between different containers.
Container Mountpoints
---------------------
Beside the root directory the container can also have additional mountpoints. Mount Points
Currently there are basically three types of mountpoints: storage backed ~~~~~~~~~~~~
mountpoints, bind mounts and device mounts.
Storage backed mountpoints are managed by the {pve} storage subsystem and come Beside the root directory the container can also have additional mount points.
Currently there are basically three types of mount points: storage backed
mount points, bind mounts and device mounts.
Storage backed mount points are managed by the {pve} storage subsystem and come
in three different flavors: in three different flavors:
- Image based: These are raw images containing a single ext4 formatted file - Image based: These are raw images containing a single ext4 formatted file
@ -355,9 +356,9 @@ advised against, as containers need to be frozen for suspend or
snapshot mode backups. If FUSE mounts cannot be replaced by other snapshot mode backups. If FUSE mounts cannot be replaced by other
mounting mechanisms or storage technologies, it is possible to mounting mechanisms or storage technologies, it is possible to
establish the FUSE mount on the Proxmox host and use a bind establish the FUSE mount on the Proxmox host and use a bind
mountpoint to make it accessible inside the container. mount point to make it accessible inside the container.
The root mountpoint is configured with the 'rootfs' property, and you can The root mount point is configured with the 'rootfs' property, and you can
configure up to 10 additional mount points. The corresponding options configure up to 10 additional mount points. The corresponding options
are called 'mp0' to 'mp9', and they can contain the following setting: are called 'mp0' to 'mp9', and they can contain the following setting:
@ -371,25 +372,29 @@ rootfs: thin1:base-100-disk-1,size=8G
Using quotas inside containers Using quotas inside containers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Quotas allow to set limits inside a container for the amount of disk space Quotas allow to set limits inside a container for the amount of disk
that each user can use. space that each user can use. This only works on ext4 image based
This only works on ext4 image based storage types and currently does not work storage types and currently does not work with unprivileged
with unprivileged containers. containers.
Activating the `quota` option causes the following mount options to be used for Activating the `quota` option causes the following mount options to be
a mountpoint: `usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0` used for a mount point:
`usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0`
This allows quotas to be used like you would on any other system. You can This allows quotas to be used like you would on any other system. You
initialize the `/aquota.user` and `/aquota.group` files by running can initialize the `/aquota.user` and `/aquota.group` files by running
quotacheck -cmug / ----
quotaon / quotacheck -cmug /
quotaon /
----
and edit the quotas via the `edquota` command. Refer to the documentation and edit the quotas via the `edquota` command. Refer to the documentation
of the distribution running inside the container for details. of the distribution running inside the container for details.
NOTE: You need to run the above commands for every mountpoint by passing NOTE: You need to run the above commands for every mount point by passing
the mountpoint's path instead of just `/`. the mount point's path instead of just `/`.
Using ACLs inside containers Using ACLs inside containers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~