From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] faq: mention OCI support in container technology comparison
Date: Tue, 18 Nov 2025 14:43:23 +0100 [thread overview]
Message-ID: <20251118134326.109362-1-f.schauer@proxmox.com> (raw)
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
next reply other threads:[~2025-11-18 13:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 13:43 Filip Schauer [this message]
2025-11-18 14:39 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251118134326.109362-1-f.schauer@proxmox.com \
--to=f.schauer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox