public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Filip Schauer <f.schauer@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH proxmox-perl-rs v2 02/11] add Perl mapping for OCI container image parser/extractor
Date: Wed, 25 Jun 2025 10:10:11 +0200	[thread overview]
Message-ID: <h5rgbhdugye4qghfreomy4bui356jrgxmt25v2y5hjivvt4f3g@wvhnumowjmzi> (raw)
In-Reply-To: <a740a724-6a2c-48ed-b632-f674c19c4831@proxmox.com>

On Wed, Jun 25, 2025 at 09:59:08AM +0200, Filip Schauer wrote:
> On 24/06/2025 14:51, Wolfgang Bumiller wrote:
> > > +    #[export]
> > > +    pub fn parse_and_extract_image(
> > > +        oci_tar_path: &str,
> > > +        rootfs_path: &str,
> > > +    ) -> Result<Option<Config>, Error> {
> > > +        match proxmox_oci::parse_and_extract_image(oci_tar_path, rootfs_path) {
> > > +            Ok(config) => Ok(Some(config.unwrap_or_default())),
> > > +            Err(err) => match err {
> > > +                ProxmoxOciError::ParseError(ParseError::NotAnOciImage(_)) => Ok(None),
> > ^ Why are we doing this?
> 
> In the Perl code of the create_vm API method at PVE::API2::LXC, if a
> .tar file is used as the container template,
> PVE::RS::OCI::parse_and_extract_image is first attempted.
> It returns undef, when the .tar file is not an OCI image. Thus we deduce
> that the file is an LXC template. If some other kind of error occurrs,
> (e.g. I/O error) then the Perl code should die.
> 
> The point is, there needs to be a way to differentiate between the file
> actually being an LXC template, and some general failure.

Given how the errors in the oci-spec work I think it would make more
sense to do this detection separately by simply looking for an
`oci-layout` file in the archive (or looking for all of `oci-layout`,
`blobs`, `index.json` at only the top level).

An an error in the OCI data should not cause us to try to extract this
as a regular container either.

In the long run, this needs to be a separate content type anyway, since
don't want to just extract tar files like this. Rather, we want to later
also add the ability to use the base image via overlayfs.


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


  reply	other threads:[~2025-06-25  8:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 14:48 [pve-devel] [PATCH container/manager/proxmox{, -perl-rs}/storage v2 00/11] support OCI images as container templates Filip Schauer
2025-06-11 14:48 ` [pve-devel] [PATCH proxmox v2 01/11] add proxmox-oci crate Filip Schauer
2025-06-24 12:42   ` Wolfgang Bumiller
2025-06-25  8:13   ` Wolfgang Bumiller
2025-06-11 14:48 ` [pve-devel] [PATCH proxmox-perl-rs v2 02/11] add Perl mapping for OCI container image parser/extractor Filip Schauer
2025-06-24 12:51   ` Wolfgang Bumiller
2025-06-25  7:59     ` Filip Schauer
2025-06-25  8:10       ` Wolfgang Bumiller [this message]
2025-06-11 14:48 ` [pve-devel] [PATCH container v2 03/11] config: whitelist lxc.init.cwd Filip Schauer
2025-06-25  9:00   ` [pve-devel] applied: " Wolfgang Bumiller
2025-06-11 14:48 ` [pve-devel] [PATCH container v2 04/11] add support for OCI images as container templates Filip Schauer
2025-06-11 14:48 ` [pve-devel] [PATCH container v2 05/11] config: add entrypoint parameter Filip Schauer
2025-06-11 14:48 ` [pve-devel] [PATCH container v2 06/11] configure static IP in LXC config for custom entrypoint Filip Schauer
2025-06-25  8:26   ` Wolfgang Bumiller
2025-06-25  8:30     ` Wolfgang Bumiller
2025-06-25  8:52       ` Stefan Hanreich
2025-07-09 12:45     ` Filip Schauer
2025-06-11 14:48 ` [pve-devel] [PATCH container v2 07/11] setup: debian: create /etc/network path if missing Filip Schauer
2025-06-11 14:49 ` [pve-devel] [PATCH container v2 08/11] setup: recursively mkdir /etc/systemd/{network, system-preset} Filip Schauer
2025-06-11 14:49 ` [pve-devel] [PATCH container v2 09/11] manage DHCP for containers with custom entrypoint Filip Schauer
2025-06-25  8:50   ` Wolfgang Bumiller
2025-07-09 12:43     ` Filip Schauer
2025-07-09 13:00       ` Wolfgang Bumiller
2025-06-11 14:49 ` [pve-devel] [PATCH storage v2 10/11] allow .tar container templates Filip Schauer
2025-06-24 13:11   ` Wolfgang Bumiller
2025-06-11 14:49 ` [pve-devel] [PATCH manager v2 11/11] ui: storage upload: accept *.tar files as vztmpl Filip Schauer
2025-06-17  8:01 ` [pve-devel] [PATCH container/manager/proxmox{, -perl-rs}/storage v2 00/11] support OCI images as container templates Christoph Heiss
2025-07-09 12:50   ` Filip Schauer
2025-07-09 12:40 ` [pve-devel] superseded: " Filip Schauer

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=h5rgbhdugye4qghfreomy4bui356jrgxmt25v2y5hjivvt4f3g@wvhnumowjmzi \
    --to=w.bumiller@proxmox.com \
    --cc=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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal