public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container] setup: support Ubuntu 24.04 Noble
Date: Tue, 30 Apr 2024 10:43:14 +0200	[thread overview]
Message-ID: <60e2a7c7-98d7-4ba3-9548-f31635da7629@proxmox.com> (raw)
In-Reply-To: <5a6f03ef-e673-4612-bb80-eb2509930850@proxmox.com>

Am 29.04.24 um 13:11 schrieb Thomas Lamprecht:
> Am 29/04/2024 um 11:56 schrieb Fiona Ebner:
>> Am 29.04.24 um 11:36 schrieb Fiona Ebner:
>>> Am 29.04.24 um 11:23 schrieb Fiona Ebner:
>>>> Reported in the community forum:
>>>> https://forum.proxmox.com/threads/145848/#post-658694
>>>>
>>>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>>>> ---
>>>>
>>>> Minimally tested, that an upgrade from an existing 23.04 container
>>>> works, there still is network and no obviously bad messages in the
>>>> container's journal.
>>>>
>>> Hmm, while the upgrade did work, starting from an Ubuntu 24.04 template
>>> and setting a static IP does not seem to work, like described here:
>>> https://forum.proxmox.com/threads/145848/post-658058
>>
>> Seems like the ordering of the configuration files is the issue. The
>> following would fix it, but probably needs to be special-cased for new
>> Ubuntu (or new systemd, would still need to check where the change came
>> in exactly) not to mess up existing containers, right?
> 
> Yes, at least that would reduce regression potential of unknown issues.

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.


_______________________________________________
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:43 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 [this message]
2024-04-30  8:59         ` Thomas Lamprecht
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=60e2a7c7-98d7-4ba3-9548-f31635da7629@proxmox.com \
    --to=f.ebner@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 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