Explain how PVE containers use LXC in the FAQ.

[pve-docs.git] / pve-faq.adoc

diff --git a/pve-faq.adoc b/pve-faq.adoc
index 738092f447308c643d5b1f7e1b0a02cd8a9df482..82709093e0ae8c151e653cc62bdee88538b37731 100644 (file)
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -1,5 +1,5 @@
 Frequently Asked Questions
---------------------------
+==========================
 include::attributes.txt[]
 
 NOTE: New FAQs are appended to the bottom of this section.
@@ -52,7 +52,7 @@ What is a container, CT, VE, Virtual Private Server, VPS?::
 Operating-system-level virtualization is a server-virtualization
 method where the kernel of an operating system allows for multiple
 isolated user-space instances, instead of just one. We call such
-instances containers. As containers share the Kernel they are
+instances containers. As containers use the host's kernel they are
 limited to Linux guests.
 
 What is a QEMU/KVM guest (or VM)?::
@@ -68,3 +68,49 @@ native performance by executing the guest code directly on the host
 CPU.
 It is not limited to Linux guests but allows arbitrary operating systems
 to run.
+
+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} 4.x     | Debian 8 (Jessie) | 2015-10       | 2018-05    | tba
+| {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
+|===========================================================
+
+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.
++
+LXD is building 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.
++
+LXC, as well as the former OpenVZ, aims at *system virtualization*, ie
+allows you to run a complete OS inside a container, where you log in as ssh,
+add users, run apache, etc...
++
+Proxmox VE aims at system virtualization, and thus uses LXC as the basis of its
+own container offer. LXC provides countless options, and it would be too
+difficult to use LXC tools directly. Instead, we provide a small wrapper called
+`pct`, the "Proxmox Container Toolkit", using LXC as a low-level library.
++
+Docker aims at running a *single* application running in a contained
+environment. Hence you're managing a docker instance from the host with the
+docker toolkit.
++
+NOTE: You can however perfectly install and use docker inside a Proxmox Qemu
+VM, and thus getting the benefit of software containerization with the very
+strong isolation that VMs provide.