all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Daniel Kral <d.kral@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH container v2 3/4] setup: add no-op detect_architecture for unmanaged CTs
Date: Fri, 6 Feb 2026 14:09:17 +0100	[thread overview]
Message-ID: <5a6b230c-0de8-4e99-959d-55c4649f0d85@proxmox.com> (raw)
In-Reply-To: <20260206124513.310674-4-d.kral@proxmox.com>

Am 06.02.26 um 1:44 PM schrieb Daniel Kral:
> This plugin method is only called in PVE::LXC::Setup::new() and is
> wrapped in an eval block, so it won't fail to create the container, but
> report an error that the plugin method is not implemented for unmanaged
> containers.
> 
> Signed-off-by: Daniel Kral <d.kral@proxmox.com>
> ---
> changes from v1:
>   - none
> 
>  src/PVE/LXC/Setup/Unmanaged.pm | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/src/PVE/LXC/Setup/Unmanaged.pm b/src/PVE/LXC/Setup/Unmanaged.pm
> index aa26c1c..b51be55 100644
> --- a/src/PVE/LXC/Setup/Unmanaged.pm
> +++ b/src/PVE/LXC/Setup/Unmanaged.pm
> @@ -65,6 +65,11 @@ sub ssh_host_key_types_to_generate {
>      return;
>  }
>  
> +sub detect_architecture {
> +    my ($self) = @_;
> +    return;

Thinking through it again, should we rather just die here instead of
returning undef? It seems to me that the contract for the method is
currently "either return the detected architecture or die". Then patch
4/4 would not be needed. Your new implementation adds a "or return
undef" to the contract making it more complicated.

> +}
> +
>  # hooks
>  
>  sub pre_start_hook {





  reply	other threads:[~2026-02-06 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 12:45 [PATCH-SERIES container v2 0/4] add missing no-op methods " Daniel Kral
2026-02-06 12:45 ` [PATCH container v2 1/4] setup: plugin: add missing check_systemd_nesting stub Daniel Kral
2026-02-06 12:45 ` [PATCH container v2 2/4] fix #7270: setup: add no-op check_systemd_nesting for unmanaged CTs Daniel Kral
2026-02-06 12:45 ` [PATCH container v2 3/4] setup: add no-op detect_architecture " Daniel Kral
2026-02-06 13:09   ` Fiona Ebner [this message]
2026-02-06 14:30     ` Thomas Lamprecht
2026-02-06 15:04       ` Fiona Ebner
2026-02-06 14:30   ` applied: " Thomas Lamprecht
2026-02-06 12:45 ` [PATCH container v2 4/4] setup: make the architecture fall back to amd64 for falsy values Daniel Kral
2026-02-06 14:30   ` applied: " Thomas Lamprecht
2026-02-06 13:18 ` partially-applied: [PATCH-SERIES container v2 0/4] add missing no-op methods for unmanaged CTs Fiona Ebner

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=5a6b230c-0de8-4e99-959d-55c4649f0d85@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=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