public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Kaiyang Wu <wukaiyang2003@gmail.com>
Cc: pve-devel@lists.proxmox.com, Kaiyang Wu <wukaiyang@loongfans.cn>
Subject: Re: [PATCH container] setup: fedora: disable static units when fixing up template
Date: Wed, 29 Jul 2026 11:21:30 +0200	[thread overview]
Message-ID: <s8o5x1ycfs5.fsf@toolbox> (raw)
In-Reply-To: <7ecdfb8e-e15a-4ba3-a71f-b855cd0b64ce@gmail.com> (Kaiyang Wu's message of "Wed, 29 Jul 2026 17:03:02 +0800")

Kaiyang Wu <wukaiyang2003@gmail.com> writes:

> Hi Maximiliano,
>
> Thank you for your fast reply, here's the information:
> 1. Fedora 43
> 2. The Fedora container image is the official template shipped by PVE
> (fedora-43-default_20261115_amd64.tar.xz)
> 3. The units always fail after booting the container. I set the container up
> with the default options.
>
> Best,
> Kaiyang

Thanks for the details.

I can confirm this is reproducible with the fedora 43 and fedora 44
images on our templates.

    # 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

In both cases with /sys/kernel/config: permission denied.

I tested that the patch fixes the issue on the fedora 43 image.

Tested-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
Reviewed-by: Maximiliano Sandoval <m.sandoval@proxmox.com>

-- 
Maximiliano




      reply	other threads:[~2026-07-29  9:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 10:10 [PATCH container] setup: fedora: disable static units when fixing up template wukaiyang2003
2026-07-13  3:16 ` Kaiyang Wu
2026-07-29  8:41   ` Kaiyang Wu
2026-07-29  8:56     ` Maximiliano Sandoval
2026-07-29  9:03       ` Kaiyang Wu
2026-07-29  9:21         ` Maximiliano Sandoval [this message]

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=s8o5x1ycfs5.fsf@toolbox \
    --to=m.sandoval@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=wukaiyang2003@gmail.com \
    --cc=wukaiyang@loongfans.cn \
    /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