Ubuntu 24.04 - unsupported Ubuntu version '24.04'

[jasonsansone]

I can confirm that nesting fixes the problem on a test container, but I am reluctant to run nested and privileged on anything but a test environment.

 

[jasonsansone]

I can confirm that nesting fixes the problem on a test container, but I am reluctant to run nested and privileged on anything but a test environment.

Any potential fixes in testing?

 

[JinTO]

Doesn't seem to matter if the container is privileged or not.
I tried both ways and still get:

extracting archive '/mnt/pve/Hermes_NFS/template/cache/ubuntu-24.04-standard_24.04-2_amd64.tar.zst'
Total bytes read: 564490240 (539MiB, 212MiB/s)
TASK ERROR: unable to create CT 102 - unsupported Ubuntu version '24.04'

 

[davidgamer]

I'm still not able to log in to the shell after creating the container as well. I've attached the log details in here as well.

 

[fiona]

Hi,

Doesn't seem to matter if the container is privileged or not.
I tried both ways and still get:

extracting archive '/mnt/pve/Hermes_NFS/template/cache/ubuntu-24.04-standard_24.04-2_amd64.tar.zst'
Total bytes read: 564490240 (539MiB, 212MiB/s)
TASK ERROR: unable to create CT 102 - unsupported Ubuntu version '24.04'

then you are not using a recent enough version of the pve-container package, i.e. >= 5.1.10. You'll need to upgrade that first.

 

[fiona]

Any potential fixes in testing?

Unfortunately, it seems like there is nothing that can be done. The new systemd that comes with Ubuntu 24.04 wants to do namespacing, so nesting is required. I suggest you migrate your untrusted containers to be unprivileged instead.

 

[fiona]

Hi,

I'm still not able to log in to the shell after creating the container as well. I've attached the log details in here as well.

if the container is privileged, see the previous messages in this thread.

If the container is unprivileged, please share the output of

pct config 210
pct start 210 --debug
pveversion -v

 

[davidgamer]

Hi,

if the container is privileged, see the previous messages in this thread.

If the container is unprivileged, please share the output of

pct config 210
pct start 210 --debug
pveversion -v

OK got it.

I created a privileged container and after creating it enabled nesting and that enabled it to start up. Initially in the creation screen, checking or unchecking the nesting feature has no effect at first start up. So I had to manually enable nesting then it would load up correctly.

The unprivileged container started up no problems.

So it sounds like we will be stuck with having nesting enabled on unprivileged Ubuntu 24.04. Hopefully there is a way to get it without nesting since this is an LTS release, I was hoping to keep it around for a while.