all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] Proposal For Podman Container Support
Date: Tue, 18 Mar 2025 14:10:22 +0100	[thread overview]
Message-ID: <8ec9aa5a-23ee-469c-85af-8e4ec607a3bd@proxmox.com> (raw)
In-Reply-To: <026ab4f3-d6ed-4a7f-8043-34b8a7a1b589@proxmox.com>

On 3/18/25 13:32, Filip Schauer wrote:
> Hello,
> 
> I have skimmed through the OCI Runtime+Image specs.
> Here is a rough outline of OCI Runtime Bundles and OCI Images:

Hi!

Just to add to the discussion about this feature: On my very narrow 
search about existing solutions for creating LXC containers from OCI 
images, I came across a builtin script for LXC for this [0]. This 
"template" can be used with lxc-create, e.g.

$ lxc-create <lxc-name> -t oci -- --url docker://myimage:latest

AFAIK we don't use lxc-create when setting up LXC containers, but maybe 
there's some useful information in parsing and integrating OCI image 
imports for Proxmox VE in there. But I haven't spent much time going 
through the script, so a closer look is needed to evaluate this.

Kind regards,
     Daniel

[0] https://github.com/lxc/lxc/blob/main/templates/lxc-oci.in


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-03-18 13:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e0a39815-26cc-4530-9bcd-5e5e2f1f1ae4@disroot.org>
2025-03-18  9:45 ` Thomas Lamprecht
2025-03-18 12:32   ` Filip Schauer
2025-03-18 13:10     ` Daniel Kral [this message]
2025-05-20 12:48     ` Filip Schauer
2025-05-25  6:27       ` Raven King via pve-devel
2025-03-18 16:23   ` Raven King via pve-devel
2025-03-13 18:03 Raven King via pve-devel

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=8ec9aa5a-23ee-469c-85af-8e4ec607a3bd@proxmox.com \
    --to=d.kral@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal