From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pct: application containers: fix classification as technology preview
Date: Wed, 19 Nov 2025 09:42:05 +0100 [thread overview]
Message-ID: <20251119084244.43529-1-f.weber@proxmox.com> (raw)
Mention technology preview also in the introductory paragraph, and fix
an incomplete sentence in the "Open Container Initiative (OCI) Images"
section.
Signed-off-by: Friedrich Weber <f.weber@proxmox.com>
---
Notes:
best viewed with --word-diff
pct.adoc | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/pct.adoc b/pct.adoc
index fe656d8..d68a4ed 100644
--- a/pct.adoc
+++ b/pct.adoc
@@ -58,10 +58,10 @@ Our primary goal has traditionally been to offer an environment that provides
the benefits of using a VM, but without the additional overhead. This means that
Proxmox Containers have been primarily categorized as ``System Containers''.
-With the introduction of OCI (**O**pen **C**ontainer **I**nitiative) image support,
-Proxmox VE now also integrates ``Application Containers''. When creating a
-container from an OCI image, the image is automatically converted to the
-LXC stack that Proxmox VE uses.
+With the introduction of OCI (**O**pen **C**ontainer **I**nitiative) image
+support, Proxmox VE now also integrates ``Application Containers'' as a
+technology preview. When creating a container from an OCI image, the image is
+automatically converted to the LXC stack that Proxmox VE uses.
This approach allows users to benefit from a wide ecosystem of pre-packaged
applications while retaining the robust management features of Proxmox VE.
@@ -353,8 +353,8 @@ Open Container Initiative (OCI) Images
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
{pve} can also use OCI images to create containers, both system containers but
-also application containers. Note that running application in {pve} is currently
-considered a (technology preview.
+also application containers. Note that running application containers in {pve}
+is currently considered a technology preview.
A container created from an OCI image still uses the existing LXC framework.
--
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-19 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 8:42 Friedrich Weber [this message]
2025-11-19 9:22 ` [pve-devel] applied: " 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=20251119084244.43529-1-f.weber@proxmox.com \
--to=f.weber@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