CT Templates: Fedora 34 EOL and new Fedora 36?

[lukyjay]

Hi

Fedora 34 is going end-of-life this week and Fedora 36 has been released.

Will Fedora 34 template be removed, and will 36 be added? I tried updating my templates and I'm still seeing 34 and 35.

I converted to Fedora for v36 on the desktop and I absolutely love it so I'd like to try moving from Debian containers to Fedora ones.

Thank you
J

 

[lukyjay]

Bumping

 

[lukyjay]

Anyone?

 

[lukyjay]

@martin should I raise a ticket in the bug tracker? Just looking for a reply even if it's a no so I know what the options are

 

[skyblaster]

For those of you who may be running podman nested inside LXC, you may find issues running "podman info".
See: https://github.com/containers/podman/issues/14472

Also looking forward to a native f36 container. I didn't have any luck with the base images provided here: https://koji.fedoraproject.org/koji/packageinfo?packageID=26387

 

[skyblaster]

@lukyjay If you're still looking for something to test with while waiting for an "official" image, the latest from here worked for me.

 

[lukyjay]

@lukyjay If you're still looking for something to test with while waiting for an "official" image, the latest from here worked for me.

Thank you

It looks like it's listed as being supported on the LXC pages too. I have raised a ticket in the bug tracker to see if it can be added to the GUI / pveam

https://bugzilla.proxmox.com/show_bug.cgi?id=4108

 

[skyblaster]

New official image is available. Thanks @oguz

In an unprivileged container with features "fuse=1,keyctl=1,nesting=1", I'm seeing the following failed systemd mounts.

# systemctl --failed
  UNIT                    LOAD   ACTIVE SUB    DESCRIPTION                     
● sys-kernel-config.mount loaded failed failed Kernel Configuration File System
● sys-kernel-debug.mount  loaded failed failed Kernel Debug File System

# systemctl status sys-kernel-config.mount
× sys-kernel-config.mount - Kernel Configuration File System
     Loaded: loaded (/usr/lib/systemd/system/sys-kernel-config.mount; static)
     Active: failed (Result: exit-code) since Sat 2022-06-25 21:14:01 UTC; 5min ago
      Where: /sys/kernel/config
       What: configfs
       Docs: https://www.kernel.org/doc/Documentation/filesystems/configfs/configfs.txt
             https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
        CPU: 2ms

Jun 25 21:14:01 fedora36 mount[75]: mount: /sys/kernel/config: permission denied.
Jun 25 21:14:01 fedora36 mount[75]:        dmesg(1) may have more information after failed mount system call.
Notice: journal has been rotated since unit was started, output may be incomplete.

# systemctl status sys-kernel-debug.mount
× sys-kernel-debug.mount - Kernel Debug File System
     Loaded: loaded (/usr/lib/systemd/system/sys-kernel-debug.mount; static)
     Active: failed (Result: exit-code) since Sat 2022-06-25 21:14:01 UTC; 6min ago
      Where: /sys/kernel/debug
       What: debugfs
       Docs: https://www.kernel.org/doc/Documentation/filesystems/debugfs.txt
             https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
        CPU: 3ms

Jun 25 21:14:01 fedora36 mount[66]: mount: /sys/kernel/debug: permission denied.
Jun 25 21:14:01 fedora36 mount[66]:        dmesg(1) may have more information after failed mount system call.
Notice: journal has been rotated since unit was started, output may be incomplete.

I spun up a Fedora 35 container and found the same two failed units.
Unfortunately a forum search didn't turn up any answers to properly resolving these messages.