From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH container] fix regression breaking container restore from PBS
Date: Tue, 18 Nov 2025 10:07:12 +0100 [thread overview]
Message-ID: <1763456798.8giibczwqm.astroid@yuna.none> (raw)
In-Reply-To: <6d91f4e1-33e3-49cf-a405-723b4f40d305@proxmox.com>
On November 17, 2025 7:40 pm, Thomas Lamprecht wrote:
> Am 17.11.25 um 14:53 schrieb Fabian Grünbichler:
>> we should have
>>
>> PVE::LXC::archive_is_oci_format($storage_cfg, $archive)
>>
>> and then we can just inline that and have a combined
>>
>> PVE::LXC::restore_oci_archive($storage_cfg, $archive, $conf)
>>
>> that combines the two current helpers (extract_oci_config and
>> merge_oci_conf_into_pct_conf) which are both only called once..
>
> Ack.
>
>> and we end up with
>>
>> if ($restore && $archive ne '-') {
>> print "restoring '$archive' now..\n";
>> } elsif (PVE::LXC::archive_is_oci_format($storage_cfg, $archive) {
>> print "Detected OCI archive\n";
>> PVE::LXC::restore_oci_archive($storage_cfg, $archive, $conf);
>> } else {
>> # Not an OCI image, so restore it as an LXC image instead
>> PVE::LXC::Create::restore_archive(
>>
>
> This if-elsif-else chain is wrong though, i.e., the first one needs to be separate,
> and can move in the else branch. I ended up with:
>
> if (
> !$restore # OCI image format is solely supported for fresh creation.
> && PVE::LXC::Create::archive_is_oci_format($storage_cfg, $archive)
> ) {
> print "Detected OCI archive\n";
> PVE::LXC::Create::restore_oci_archive(
> $storage_cfg, $archive, $rootdir, $conf,
> );
> } else {
> print "restoring '$archive' now..\n" if $restore && $archive ne '-';
> ....
>
> I'd appreciate another look though!
Yes, Filip also noted that off-list yesterday, sorry!
changes look good to me.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-18 9:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 11:30 Filip Schauer
2025-11-17 11:58 ` Christian Ebner
2025-11-17 12:22 ` Filip Schauer
2025-11-17 13:54 ` Fabian Grünbichler
2025-11-17 18:40 ` Thomas Lamprecht
2025-11-18 9:07 ` Fabian Grünbichler [this message]
2025-11-17 13:54 ` [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=1763456798.8giibczwqm.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.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 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.