pve-installation.adoc: reorder, cleanups

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

diff --git a/pve-faq.adoc b/pve-faq.adoc
index baa8e7fd198cbb7fe62d095eea78a4dd076be320..9489295b8621388d70244b5a70b4880ceb87661d 100644 (file)
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -1,5 +1,6 @@
 Frequently Asked Questions
 Frequently Asked Questions

---------------------------
+==========================
+include::attributes.txt[]

 
 NOTE: New FAQs are appended to the bottom of this section.
 
 
 NOTE: New FAQs are appended to the bottom of this section.
 


@@ -20,15 +21,15 @@ version 3.
 
 Will {pve} run on a 32bit processor?::
 
 
 Will {pve} run on a 32bit processor?::
 

-{pve} works only on 64-bit CPU´s (AMD or Intel). There is no plan
+{pve} works only on 64-bit CPUs (AMD or Intel). There is no plan

 for 32-bit for the platform.
 +
 NOTE: VMs and Containers can be both 32-bit and/or 64-bit.
 
 Does my CPU support virtualization?::
 
 for 32-bit for the platform.
 +
 NOTE: VMs and Containers can be both 32-bit and/or 64-bit.
 
 Does my CPU support virtualization?::
 

-To check if your CPU is virtualization compatible, check for the "vmx"
-or "svm" tag in this command output:
+To check if your CPU is virtualization compatible, check for the `vmx`
+or `svm` tag in this command output:

 +
 ----
 egrep '(vmx|svm)' /proc/cpuinfo
 +
 ----
 egrep '(vmx|svm)' /proc/cpuinfo


@@ -51,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
 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)?::
 limited to Linux guests.
 
 What is a QEMU/KVM guest (or VM)?::


@@ -67,3 +68,53 @@ 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.
 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. LXC, as well as the former
+OpenVZ, aims at *system virtualization*, i.e. allows you to run a
+complete OS inside a container, where you log in as ssh, add users,
+run apache, etc...
++
+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.
++
+Proxmox Containers also aims at *system virtualization*, and thus uses
+LXC as the basis of its own container offer. The Proxmox Container
+Toolkit is called `pct`, and is tightly coupled with {pve}. That means
+that it is aware of the cluster setup, and it can use the same network
+and storage resources as fully virtualized 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 running in a contained
+environment. Hence you're managing a docker instance from the host with the
+docker toolkit. It is not recommended to run docker directly on your
+{pve} host.
++
+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.