+It is not limited to Linux guests but allows arbitrary operating systems
+to run.
+
+[[faq-support-table]]
+How long will my {pve} version be supported?::
+
+{pve} versions are supported at least as long as the corresponding
+Debian Version is
+https://wiki.debian.org/DebianOldStable[oldstable]. {pve} uses a
+rolling release model and using the latest stable version is always
+recommended.
++
+[width="100%",cols="5*d",options="header"]
+|===============================================================================
+| {pve} Version | Debian Version | First Release | Debian EOL | Proxmox EOL
+| {pve} 7.x | Debian 11 (Bullseye)| 2021-07 | tba | tba
+| {pve} 6.x | Debian 10 (Buster) | 2019-07 | 2022-07 | 2022-07
+| {pve} 5.x | Debian 9 (Stretch) | 2017-07 | 2020-07 | 2020-07
+| {pve} 4.x | Debian 8 (Jessie) | 2015-10 | 2018-06 | 2018-06
+| {pve} 3.x | Debian 7 (Wheezy) | 2013-05 | 2016-04 | 2017-02
+| {pve} 2.x | Debian 6 (Squeeze) | 2012-04 | 2014-05 | 2014-05
+| {pve} 1.x | Debian 5 (Lenny) | 2008-10 | 2012-03 | 2013-01
+|===============================================================================
+
+[[faq-upgrade]]
+How can I upgrade {pve} to the next release?::
+
+Minor version upgrades, for example upgrading from {pve} in version 5.1
+to 5.2, can be done just like any normal update, either through the Web
+GUI __Node -> Updates__ panel or through the CLI with:
++
+----
+apt update
+apt full-upgrade
+----
++
+NOTE: Always ensure you correctly setup the
+xref:sysadmin_package_repositories[package repositories] and only
+continue with the actual upgrade if `apt update` did not hit any error.
++
+Major version upgrades, for example going from {pve} 4.4 to 5.0, are
+also supported. They must be carefully planned and tested and should
+*never* be started without having a current backup ready.
+Although the specific upgrade steps depend on your respective setup, we
+provide general instructions and advice of how a upgrade should be
+performed:
++
+* https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0[Upgrade from {pve} 6.x to 7.0]
+
+* https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0[Upgrade from {pve} 5.x to 6.0]
+
+* https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0[Upgrade from {pve} 4.x to 5.0]
+
+* https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0[Upgrade from {pve} 3.x to 4.0]
+
+LXC vs LXD vs Proxmox Containers vs Docker::
+
+LXC is a userspace interface for the Linux kernel containment
+features. Through a powerful API and simple tools, it lets Linux users
+easily create and manage system containers. LXC, as well as the former
+OpenVZ, aims at *system virtualization*. Thus, it allows you to run a
+complete OS inside a container, where you log in using ssh, add users,
+run apache, etc...
++
+LXD is built on top of LXC to provide a new, better user
+experience. Under the hood, LXD uses LXC through `liblxc` and its Go
+binding to create and manage the containers. It's basically an
+alternative to LXC's tools and distribution template system with the
+added features that come from being controllable over the network.
++
+Proxmox Containers are how we refer to containers that are created and managed
+using the Proxmox Container Toolkit (`pct`). They also target *system
+virtualization* and use LXC as the basis of the container offering. The
+Proxmox Container Toolkit (`pct`) is tightly coupled with {pve}. This means
+that it is aware of cluster setups, and it can use the same network
+and storage resources as QEMU virtual machines (VMs). You can even use the
+{pve} firewall, create and restore backups, or manage containers using
+the HA framework. Everything can be controlled over the network using
+the {pve} API.
++
+Docker aims at running a *single* application in an isolated, self-contained
+environment. These are generally referred to as ``Application Containers'', rather
+than ``System Containers''. You manage a Docker instance from the host, using the
+Docker Engine command line interface. It is not recommended to run docker
+directly on your {pve} host.
++
+NOTE: If you want to run application containers, for example, 'Docker' images, it
+is best to run them inside a Proxmox Qemu VM.
projects / pve-docs.git / blobdiff