mirror of
https://git.proxmox.com/git/pve-docs
synced 2025-06-14 07:46:44 +00:00
improve lxc/pct faqs
This commit is contained in:
parent
99d2e25b7b
commit
8e5f15bedc
36
pve-faq.adoc
36
pve-faq.adoc
@ -89,27 +89,31 @@ recommended.
|
|||||||
LXC vs LXD vs Proxmox Containers vs Docker::
|
LXC vs LXD vs Proxmox Containers vs Docker::
|
||||||
|
|
||||||
LXC is a userspace interface for the Linux kernel containment
|
LXC is a userspace interface for the Linux kernel containment
|
||||||
features. Through a powerful API and simple tools, it lets Linux users easily
|
features. Through a powerful API and simple tools, it lets Linux users
|
||||||
create and manage system containers.
|
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
|
LXD is building on top of LXC to provide a new, better user
|
||||||
the hood, LXD uses LXC through liblxc and its Go binding to create and manage
|
experience. Under the hood, LXD uses LXC through 'liblxc' and its Go
|
||||||
the containers. It's basically an alternative to LXC's tools and distribution
|
binding to create and manage the containers. It's basically an
|
||||||
template system with the added features that come from being controllable over
|
alternative to LXC's tools and distribution template system with the
|
||||||
the network.
|
added features that come from being controllable over the network.
|
||||||
+
|
+
|
||||||
LXC, as well as the former OpenVZ, aims at *system virtualization*, ie
|
Proxmox Containers also aims at *system virtualization*, and thus uses
|
||||||
allows you to run a complete OS inside a container, where you log in as ssh,
|
LXC as the basis of its own container offer. The Proxmox Container
|
||||||
add users, run apache, etc...
|
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
|
||||||
Proxmox VE aims at system virtualization, and thus uses LXC as the basis of its
|
and storage resources as fully virtualized VMs. You can even use the
|
||||||
own container offer. LXC provides countless options, and it would be too
|
{pve} firewall, create and restore backups, or manage containers using
|
||||||
difficult to use LXC tools directly. Instead, we provide a small wrapper called
|
the HA framework. Everything can be controlled over the network using
|
||||||
`pct`, the "Proxmox Container Toolkit", using LXC as a low-level library.
|
the {pve} API.
|
||||||
+
|
+
|
||||||
Docker aims at running a *single* application running in a contained
|
Docker aims at running a *single* application running in a contained
|
||||||
environment. Hence you're managing a docker instance from the host with the
|
environment. Hence you're managing a docker instance from the host with the
|
||||||
docker toolkit.
|
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
|
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
|
VM, and thus getting the benefit of software containerization with the very
|
||||||
|
Loading…
Reference in New Issue
Block a user