public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Raven King via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Raven King <raven@encodedbird.com>
Subject: Re: [pve-devel] Proposal For Podman Container Support
Date: Sat, 24 May 2025 23:27:17 -0700	[thread overview]
Message-ID: <mailman.3.1748154674.395.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <800da493-fef2-4897-8fe7-4b44bb341e01@proxmox.com>

[-- Attachment #1: Type: message/rfc822, Size: 4245 bytes --]

From: Raven King <raven@encodedbird.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] Proposal For Podman Container Support
Date: Sat, 24 May 2025 23:27:17 -0700
Message-ID: <c32c74a2-eb75-4217-a457-9606781d41a3@encodedbird.com>

That's a very smart approach to that. I'll look forward to seeing it.

On 5/20/25 05:48, Filip Schauer wrote:
> Sent a patch series:
> https://lore.proxmox.com/pve-devel/20250520124257.165949-1-f.schauer@proxmox.com/T/#u 
>
>
> I ended up using OCI images as container templates.
>


[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

  reply	other threads:[~2025-05-25  6:31 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
2025-05-20 12:48     ` Filip Schauer
2025-05-25  6:27       ` Raven King via pve-devel [this message]
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=mailman.3.1748154674.395.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=raven@encodedbird.com \
    --cc=t.lamprecht@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal