Add section about pveproxy certificates

[pve-docs.git] / pct.adoc

diff --git a/pct.adoc b/pct.adoc
index 82f257b69d27c090da20be43b060411682b8613c..e9f399e3196a0bea7b9ad6c06df7a96cd281e7df 100644 (file)
--- a/pct.adoc
+++ b/pct.adoc
@@ -101,11 +101,13 @@ unprivileged containers are safe by design.
 Configuration
 -------------
 
-The '/etc/pve/lxc/<CTID>.conf' files stores container configuration,
-where '<CTID>' is the numeric ID of the given container. Note that
-CTIDs < 100 are reserved for internal purposes, and CTIDs need to be
-unique cluster wide. Files are stored inside '/etc/pve/', so they get
-automatically replicated to all other cluster nodes.
+The '/etc/pve/lxc/<CTID>.conf' file stores container configuration,
+where '<CTID>' is the numeric ID of the given container. Like all
+other files stored inside '/etc/pve/', they get automatically
+replicated to all other cluster nodes.
+
+NOTE: CTIDs < 100 are reserved for internal purposes, and CTIDs need to be
+unique cluster wide.
 
 .Example Container Configuration
 ----
@@ -401,6 +403,8 @@ Similarly device mounts are not managed by the storage, but for these the
 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.
 
@@ -413,11 +417,18 @@ initialize the `/aquota.user` and `/aquota.group` files by running
  quotacheck -cmug /
  quotaon /
 
-And edit the quotas via the `edquota` command. (Note that you need to do this
-for every mountpoint by passing the mountpoint's path instead of just `/`.) Best
-see the documentation specific to the distributiont running inside the
-container.
+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
 --------------------