document /etc/gentoo-release test

[pve-docs.git] / pct.adoc

diff --git a/pct.adoc b/pct.adoc
index 05fd71363a28f92f5a7e0c53eb319a142d1508e8..9f4fde8f21c08ada87fffe481e5400e15a67a76d 100644 (file)
--- a/pct.adoc
+++ b/pct.adoc
@@ -207,26 +207,26 @@ randomize crontab:: so that cron does not start at the same time on all containe
 
 Changes made by {PVE} are enclosed by comment markers:
 
- # --- BEGIN PVE ---
- <data>
- # --- END PVE ---
-
-If no such section is found it will be inserted at a reasonable location
-in the file.
+----
+# --- BEGIN PVE ---
+<data>
+# --- END PVE ---
+----
 
-If such a section already exists it will be updated in place and will not be
-moved.
+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:
+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
 
-The above tasks are OS dependent and so they differ between different
-distributions. You can also disable all modifications entirely by manually
-setting the 'ostype' to 'unmanaged'.
+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:
@@ -243,9 +243,16 @@ ArchLinux:: test /etc/arch-release
 
 Alpine:: test /etc/alpine-release
 
+Gentoo:: test /etc/gentoo-release
+
 NOTE: Container start fails if the configured 'ostype' differs from the auto
 detected type.
 
+Options
+~~~~~~~
+
+include::pct.conf.5-opts.adoc[]
+
 
 Container Images
 ----------------
@@ -377,6 +384,12 @@ 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.
 
+WARNING: For security reasons, bind mounts should only be established
+using source directories especially reserved for this purpose, e.g., a
+directory hierarchy under `/mnt/bindmounts`. Never bind mount system
+directories like `/`, `/var` or `/etc` into a container - this poses a
+great security risk. The bind mount source path must not contain any symlinks.
+
 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: