X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pct.adoc;h=96490864aa1709f12cd259b43e54ba556afb2689;hp=e9f399e3196a0bea7b9ad6c06df7a96cd281e7df;hb=37638f5933abbe3e521b2fdeb20f52f717d75750;hpb=166e63d688e4a5f1d7da9ad913a36e09c74ed652 diff --git a/pct.adoc b/pct.adoc index e9f399e..9649086 100644 --- a/pct.adoc +++ b/pct.adoc @@ -205,9 +205,28 @@ rewrite ssh_host_keys:: so that each container has unique keys randomize crontab:: so that cron does not start at the same time on all containers -The above task depends on the OS type, so the implementation is different -for each OS type. You can also disable any modifications by manually -setting the 'ostype' to 'unmanaged'. +Changes made by {PVE} are enclosed by comment markers: + +---- +# --- BEGIN PVE --- + +# --- END PVE --- +---- + +Those markers will be inserted at a reasonable location in the +file. If such a section already exists, it will be updated in place +and will not be moved. + +Modification of a file can be prevented by adding a `.pve-ignore.` +file for it. For instance, if the file `/etc/.pve-ignore.hosts` +exists then the `/etc/hosts` file will not be touched. This can be a +simple empty file creatd via: + + # touch /etc/.pve-ignore.hosts + +Most modifications are OS dependent, so they differ between different +distributions and versions. You can completely disable modifications +by manually setting the 'ostype' to 'unmanaged'. OS type detection is done by testing for certain files inside the container: @@ -325,6 +344,95 @@ local storage inside containers with zero overhead. Such bind mounts also provide an easy way to share data between different containers. +Mount Points +~~~~~~~~~~~~ + +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: + +- Image based: These are raw images containing a single ext4 formatted file + system. +- ZFS Subvolumes: These are technically bind mounts, but with managed storage, + and thus allow resizing and snapshotting. +- Directories: passing `size=0` triggers a special case where instead of a raw + image a directory is created. + +Bind mounts are considered to not be managed by the storage subsystem, so you +cannot make snapshots or deal with quotas from inside the container, and with +unprivileged containers you might run into permission problems caused by the +user mapping, and cannot use ACLs from inside an unprivileged container. + +Similarly device mounts are not managed by the storage, but for these the +`quota` and `acl` options will be honored. + +WARNING: Because of existing issues in the Linux kernel's freezer +subsystem the usage of FUSE mounts inside a container is strongly +advised against, as containers need to be frozen for suspend or +snapshot mode backups. If FUSE mounts cannot be replaced by other +mounting mechanisms or storage technologies, it is possible to +establish the FUSE mount on the Proxmox host and use a bind +mount point to make it accessible inside the container. + +The root mount point is configured with the 'rootfs' property, and you can +configure up to 10 additional mount points. The corresponding options +are called 'mp0' to 'mp9', and they can contain the following setting: + +include::pct-mountpoint-opts.adoc[] + +.Typical Container 'rootfs' configuration +---- +rootfs: thin1:base-100-disk-1,size=8G +---- + +Using quotas inside containers +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Quotas allow to set limits inside a container for the amount of disk +space that each user can use. This only works on ext4 image based +storage types and currently does not work with unprivileged +containers. + +Activating the `quota` option causes the following mount options to be +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 initialize the `/aquota.user` and `/aquota.group` files by running + +---- +quotacheck -cmug / +quotaon / +---- + +and edit the quotas via the `edquota` command. Refer to the documentation +of the distribution running inside the container for details. + +NOTE: You need to run the above commands for every mount point by passing +the mount point's path instead of just `/`. + + +Using ACLs inside containers +~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The standard Posix Access Control Lists are also available inside containers. +ACLs allow you to set more detailed file ownership than the traditional user/ +group/others model. + + +Container Network +----------------- + +You can configure up to 10 network interfaces for a single +container. The corresponding options are called 'net0' to 'net9', and +they can contain the following setting: + +include::pct-network-opts.adoc[] + + Managing Containers with 'pct' ------------------------------ @@ -334,7 +442,7 @@ and destroy containers, and control execution (start, stop, migrate, like network configuration or memory limits. CLI Usage Examples ------------------- +~~~~~~~~~~~~~~~~~~ Create a container based on a Debian template (provided you have already downloaded the template via the webgui) @@ -364,7 +472,8 @@ set the address and gateway, while it's running Reduce the memory of the container to 512MB - pct set -memory 512 100 + pct set 100 -memory 512 + Files ------ @@ -374,62 +483,6 @@ Files Configuration file for the container ''. -Container Mountpoints ---------------------- - -Beside the root directory the container can also have additional mountpoints. -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 -in three different flavors: - -- Image based: These are raw images containing a single ext4 formatted file - system. -- ZFS Subvolumes: These are technically bind mounts, but with managed storage, - and thus allow resizing and snapshotting. -- Directories: passing `size=0` triggers a special case where instead of a raw - image a directory is created. - -Bind mounts are considered to not be managed by the storage subsystem, so you -cannot make snapshots or deal with quotas from inside the container, and with -unprivileged containers you might run into permission problems caused by the -user mapping, and cannot use ACLs from inside an unprivileged container. - -Similarly device mounts are not managed by the storage, but for these the -`quota` and `acl` options will be honored. - - -Using quotas inside containers ------------------------------- - -Quotas allow to set limits inside a container for the amount of disk space -that each user can use. -This only works on ext4 image based storage types and currently does not work -with unprivileged containers. - -Activating the `quota` option causes the following mount options to be used for -a mountpoint: `usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0` - -This allows quotas to be used like you would on any other system. You can -initialize the `/aquota.user` and `/aquota.group` files by running - - quotacheck -cmug / - quotaon / - -and edit the quotas via the `edquota` command. Refer to the documentation -of the distribution running inside the container for details. - -NOTE: You need to run the above commands for every mountpoint by passing -the mountpoint's path instead of just `/`. - -Using ACLs inside containers ----------------------------- - -The standard Posix Access Control Lists are also available inside containers. -ACLs allow you to set more detailed file ownership than the traditional user/ -group/others model. - Container Advantages -------------------- @@ -468,7 +521,7 @@ Technology Overview - CRIU: for live migration (planned) -- We use latest available kernels (4.2.X) +- We use latest available kernels (4.4.X) - Image based deployment (templates)