public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>
Subject: Re: [pve-devel] [PATCH container] setup: support Ubuntu 24.04 Noble
Date: Tue, 30 Apr 2024 10:59:31 +0200	[thread overview]
Message-ID: <4e9d0f50-3ff9-4389-8ae8-17107e62ccd5@proxmox.com> (raw)
In-Reply-To: <60e2a7c7-98d7-4ba3-9548-f31635da7629@proxmox.com>

On 30/04/2024 10:43, Fiona Ebner wrote:
> So this is not new (already present for Ubuntu 23.10) and stems from the
> fact that these images from linuxcontainers.org contain:
> 
>> root@CT113:~# cat /etc/netplan/10-lxc.yaml 
>> network:
>>   version: 2
>>   ethernets:
>>     eth0:
>>       dhcp4: true
>>       dhcp-identifier: mac
> 
> and that generates a configuration that will be ordered before
> ours/preferred by systemd-networkd:
> 
>> root@CT113:~# networkctl status eth0
>> ● 2: eth0                                                                      
>>                      Link File: n/a
>>                   Network File: /run/systemd/network/10-netplan-eth0.network
> 
> Should we still change something in the setup code? I suppose our
> template will not have the netplan configuration file and in a way it'd
> just be a race to the bottom of being ordered first.

Why should there be a incentive for a race to the bottom?

If we have users running into this then yes, we should do something
about it, we do not have a hard requirement of the Ubuntu templates
being build through DAB and especially as we use the LXC template
builder (or well its artefacts) for other non-Debian images, I'd
see why users take it as a source.

If the change in ordering is the correct solution I cannot say without
looking into all deeper – but I'm sure you can evaluate that.
One possibility might be disabling netplan on CT creation, if PVE wants
to control network in another way itself.


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

  reply	other threads:[~2024-04-30  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29  9:23 Fiona Ebner
2024-04-29  9:36 ` Fiona Ebner
2024-04-29  9:56   ` Fiona Ebner
2024-04-29 11:11     ` Thomas Lamprecht
2024-04-30  8:43       ` Fiona Ebner
2024-04-30  8:59         ` Thomas Lamprecht [this message]
2024-04-30  9:18           ` 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=4e9d0f50-3ff9-4389-8ae8-17107e62ccd5@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.ebner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=w.bumiller@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