* [pve-devel] [PATCH docs] faq: mention OCI support in container technology comparison
@ 2025-11-18 13:43 Filip Schauer
2025-11-18 14:39 ` Thomas Lamprecht
0 siblings, 1 reply; 2+ messages in thread
From: Filip Schauer @ 2025-11-18 13:43 UTC (permalink / raw)
To: pve-devel
Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
---
pve-faq.adoc | 21 ++++++++++++---------
1 file changed, 12 insertions(+), 9 deletions(-)
diff --git a/pve-faq.adoc b/pve-faq.adoc
index b8cefd9..dfd5869 100644
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -161,13 +161,14 @@ 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.
+virtualization* and use LXC as the basis of the container offering. With the
+addition of OCI image support (technology preview), Proxmox VE can also create
+containers from *application-focused* OCI images. The Poxmox 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
@@ -175,5 +176,7 @@ than ``System Containers''. You manage a Docker instance from the host, using th
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.
+NOTE: While it is convenient to run ``Application Containers'' directly as
+Proxmox Containers, for use cases requiring container orchestration or live
+migration, it is still recommended to run them inside a Proxmox QEMU virtual
+machine.
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-11-18 14:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-11-18 13:43 [pve-devel] [PATCH docs] faq: mention OCI support in container technology comparison Filip Schauer
2025-11-18 14:39 ` Thomas Lamprecht
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox