From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 02A681FF187 for ; Tue, 18 Nov 2025 14:43:32 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AC46D150FE; Tue, 18 Nov 2025 14:43:34 +0100 (CET) From: Filip Schauer To: pve-devel@lists.proxmox.com Date: Tue, 18 Nov 2025 14:43:23 +0100 Message-ID: <20251118134326.109362-1-f.schauer@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763473381206 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.006 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs] faq: mention OCI support in container technology comparison X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Signed-off-by: Filip Schauer --- 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