be categorized as ``System Containers'', rather than ``Application Containers''.
NOTE: If you want to run application containers, for example, 'Docker' images, it
-is recommended that you run them inside a Proxmox Qemu VM. This will give you
+is recommended that you run them inside a Proxmox QEMU VM. This will give you
all the advantages of application containerization, while also providing the
benefits that VMs offer, such as strong isolation from the host and the ability
to live-migrate, which otherwise isn't possible with containers.
* Integrated into {pve} graphical web user interface (GUI)
-* Easy to use command line tool `pct`
+* Easy to use command-line tool `pct`
* Access via {pve} REST API
For currently supported releases see:
-https://wiki.centos.org/About/Product
+https://en.wikipedia.org/wiki/CentOS#End-of-support_schedule
Almalinux
^^^^^^^^^
{pve} itself provides a variety of basic templates for the
xref:pct_supported_distributions[most common Linux distributions]. They can be
downloaded using the GUI or the `pveam` (short for {pve} Appliance Manager)
-command line utility. Additionally, https://www.turnkeylinux.org/[TurnKey
+command-line utility. Additionally, https://www.turnkeylinux.org/[TurnKey
Linux] container templates are also available to download.
The list of available templates is updated daily through the 'pve-daily-update'
`cpuunits`: :: This is a relative weight passed to the kernel scheduler. The
larger the number is, the more CPU time this container gets. Number is relative
-to the weights of all the other running containers. The default is 1024. You
-can use this setting to prioritize some containers.
+to the weights of all the other running containers. The default is `100` (or
+`1024` if the host uses legacy cgroup v1). You can use this setting to
+prioritize some containers.
[[pct_memory]]
Since {pve} 7.0, the default is a pure 'cgroupv2' environment. Previously a
"hybrid" setup was used, where resource control was mainly done in 'cgroupv1'
with an additional 'cgroupv2' controller which could take over some subsystems
-via the 'cgroup_no_v1' kernel command line parameter. (See the
+via the 'cgroup_no_v1' kernel command-line parameter. (See the
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html[kernel
parameter documentation] for details.)
decades old OS versions just fine there.
* Switch back to the legacy 'cgroup' controller. Note that while it can be a
- valid solution, it's not a permanent one. There's a high likelihood that a
- future {pve} major release, for example 8.0, cannot support the legacy
- controller anymore.
+ valid solution, it's not a permanent one. Starting from {pve} 9.0, the legacy
+ controller will not be supported anymore.
====
[[pct_cgroup_change_version]]
TIP: If file system quotas are not required and all containers support 'cgroupv2',
it is recommended to stick to the new default.
-To switch back to the previous version the following kernel command line
+To switch back to the previous version the following kernel command-line
parameter can be used:
----
Managing Containers with `pct`
------------------------------
-The ``Proxmox Container Toolkit'' (`pct`) is the command line tool to manage
+The ``Proxmox Container Toolkit'' (`pct`) is the command-line tool to manage
{pve} containers. It enables you to create or destroy containers, as well as
control the container execution (start, stop, reboot, migrate, etc.). It can be
used to set parameters in the config file of a container, for example the