From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shymkent.ilbers.de ([unix socket]) by shymkent (Cyrus 2.5.10-Debian-2.5.10-3+deb9u2) with LMTPA; Mon, 27 Apr 2026 06:18:43 +0200 X-Sieve: CMU Sieve 2.4 Received: from mail-qt1-f185.google.com (mail-qt1-f185.google.com [209.85.160.185]) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPS id 63R4IgpJ032045 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Mon, 27 Apr 2026 06:18:42 +0200 Received: by mail-qt1-f185.google.com with SMTP id d75a77b69052e-50fbc49bef6sf103360821cf.0 for ; Sun, 26 Apr 2026 21:18:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1777263516; x=1777868316; darn=ilbers.de; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:x-original-sender :mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=x5y80qAkHWfVuMBeWbTBgfpdDEm6KdWNCV1PcnTb3P0=; b=jdZzuxOPfyv9qxOm4bxhddwyWTooVzR5EMhJzV63qsAG5l4/SiQ+tw0uLlHdmBgTPo 1QihQOd29rQd0gLrkGJ4UVKwfHAA301/H4f7l/82mW1jr71ZeCR8CHyGdruNZUDi4H3I VklubiYcF8bFKMxBpIBcps4kIZLgpQf7YCW++WISur70t6QDfu6ZuJvuSzv88oM9MxwM V5w4chqnNg706XAmXKe2NQvx0ShTmtCrM+JvIl0s/n7xSQBXiQ+iEYRqTHE5rBS/ibOW 8xD9fFyzC3icUeTkp6GCslr00ngxKir0DADWMzyYzAwA4yzHBh6QkBKjCc+5do53yzbS qVXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777263516; x=1777868316; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :x-spam-checked-in-group:list-id:mailing-list:precedence:reply-to :x-original-sender:mime-version:subject:references:in-reply-to :message-id:to:from:date:x-beenthere:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=x5y80qAkHWfVuMBeWbTBgfpdDEm6KdWNCV1PcnTb3P0=; b=o/TIm/muNAbV2wrqA0gIm/yH0IMX7pf5wCdHYx6LQDq8Npf7fJPnRmkK8z1f7mLm0k s94h6/t+Ogo+RNS9Nj/AsXYOjUfrWQ+gOAFFKRGMJyRG//RuqQpRYfZmNxmkt9+m6JLS PlZ+OTkL0BjyL8WGJOxwuRqQ7dWk42KQQ+C4KdwBQ94+i2ev88ca4Az0HFIwq/gKnDd6 4FsGRE269onLmmXqVBXvNR3qikXbjhALhWF2P+uI+WcGhVeU1UFTrZDaJAwiqCEWmhzb Lx/VI8YPk+g+oW4by7qzJin8X0SVO5mcd1QQEggtIWztHKluGDe7p1dRpq21FLYpD0dD zOGQ== X-Forwarded-Encrypted: i=1; AFNElJ+WJbZrYNgXYd29I27510GlBfbNkB0lkBsSkjEvXYj50mAzLw49Th1hLWtWjbBC3fCXZxZp@ilbers.de X-Gm-Message-State: AOJu0YwxDuZ6AUYiKho02WOfwaeRoGTLlnxchm6ORW34EZW3e+7TS43J SBPHE7UpMO25gepmGiRlZz5Z5B518b+6+zLsV1lCbRnuRTunc5/tytoO X-Received: by 2002:a05:622a:144c:b0:50f:b212:ae4a with SMTP id d75a77b69052e-50fb212b7cdmr385462441cf.6.1777263516164; Sun, 26 Apr 2026 21:18:36 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com; h="AUV6zMM+BzBuSbXIHLjPGwX4fCv8qL/fQAg3uOVjMiu532777A==" Received: by 2002:a05:6214:1d24:b0:89c:5962:3075 with SMTP id 6a1803df08f44-8ae8209006bls183591526d6.1.-pod-prod-08-us; Sun, 26 Apr 2026 21:18:35 -0700 (PDT) X-Received: by 2002:a05:6214:2f04:b0:8a2:4fea:4d44 with SMTP id 6a1803df08f44-8b0281403camr677392826d6.41.1777263514984; Sun, 26 Apr 2026 21:18:34 -0700 (PDT) Date: Sun, 26 Apr 2026 21:18:33 -0700 (PDT) From: "'Badrikesh Prusty' via isar-users" To: isar-users Message-Id: In-Reply-To: References: <20260219044406.441933-1-badrikesh.prusty@siemens.com> <2c47f23b-7944-40be-9721-0a0b88b9d78f@siemens.com> <64b54a7b-4a10-4621-a090-6f63a987f183@siemens.com> Subject: Re: [PATCH v3 0/1] image-postproc: ignore systemd preset failures MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_631976_800779142.1777263513097" X-Original-Sender: badrikesh.prusty@siemens.com X-Original-From: Badrikesh Prusty Reply-To: Badrikesh Prusty Precedence: list Mailing-list: list isar-users@googlegroups.com; contact isar-users+owners@googlegroups.com List-ID: X-Spam-Checked-In-Group: isar-users@googlegroups.com X-Google-Group-Id: 914930254986 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Status: No, score=-4.9 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_BLOCKED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, RCVD_IN_RP_CERTIFIED,RCVD_IN_RP_RNBL,RCVD_IN_RP_SAFE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: 8lT/m03N5mxD ------=_Part_631976_800779142.1777263513097 Content-Type: multipart/alternative; boundary="----=_Part_631977_1998851439.1777263513097" ------=_Part_631977_1998851439.1777263513097 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, Apologies for the delayed response. It looks like /proc and /sys are already mounted during the beginng of the= =20 do_rootfs_postprocess task via rootfs_do_mounts function. Shell function=20 run order: ``` $ grep "DEBUG: Shell" temp/log.do_rootfs_postprocess DEBUG: Shell function rootfs_do_mounts finished DEBUG: Shell function rootfs_do_qemu finished DEBUG: Shell function image_postprocess_disable_systemd_firstboot finished DEBUG: Shell function image_postprocess_sshd_key_regen finished DEBUG: Shell function image_postprocess_machine_id finished DEBUG: Shell function image_postprocess_mark finished DEBUG: Shell function image_postprocess_configure finished DEBUG: Shell function generate_sbom finished DEBUG: Shell function rootfs_postprocess_clean_package_cache finished DEBUG: Shell function rootfs_postprocess_clean_log_files finished DEBUG: Shell function rootfs_postprocess_clean_debconf_cache finished DEBUG: Shell function rootfs_postprocess_clean_pycache finished DEBUG: Shell function rootfs_postprocess_clean_ldconfig_cache finished DEBUG: Shell function rootfs_postprocess_clean_tmp finished DEBUG: Shell function rootfs_generate_manifest finished DEBUG: Shell function rootfs_export_dpkg_status finished DEBUG: Shell function rootfs_cleanup_isar_apt finished DEBUG: Shell function image_postprocess_populate_systemd_preset finished DEBUG: Shell function image_disable_systemd_networkd finished DEBUG: Shell function rootfs_do_umounts finished ```=20 Added "ls -l" to list the rootfs directories after do_mounts: (/proc and=20 /sys mounted) ``` lrwxrwxrwx 1 root root 7 Mar 2 21:50 bin -> usr/bin drwxr-xr-x 2 root root 4.0K Apr 23 06:28 boot -rwxr-xr-x 1 root root 3.5K Apr 21 11:05 chroot-setup.sh drwxr-xr-x 15 root root 3.4K Apr 23 06:27 dev drwxr-xr-x 58 root root 4.0K Apr 23 06:28 etc drwxr-xr-x 3 root root 4.0K Apr 23 06:28 home lrwxrwxrwx 1 root root 29 Apr 23 06:28 initrd.img ->=20 boot/initrd.img-6.12.78-cip19 lrwxrwxrwx 1 root root 29 Apr 23 06:28 initrd.img.old ->=20 boot/initrd.img-6.12.78-cip19 drwxr-xr-x 5 industrial industrial 4.0K Apr 21 11:05 isar-apt drwxr-xr-x 11 industrial industrial 4.0K Apr 23 06:28 isar-work lrwxrwxrwx 1 root root 7 Mar 2 21:50 lib -> usr/lib lrwxrwxrwx 1 root root 9 Mar 2 21:50 lib64 -> usr/lib64 drwxr-xr-x 2 root root 4.0K Apr 21 11:05 media drwxr-xr-x 2 root root 4.0K Apr 21 11:05 mnt drwxr-xr-x 3 root root 4.0K Apr 23 06:28 opt dr-xr-xr-x 813 root root 0 Apr 23 06:28 proc drwx------ 3 root root 4.0K Apr 23 06:28 root drwxr-xr-x 9 root root 4.0K Apr 23 06:28 run lrwxrwxrwx 1 root root 8 Mar 2 21:50 sbin -> usr/sbin drwxr-xr-x 2 root root 4.0K Apr 21 11:05 srv drwxr-xr-x 13 root root 0 Mar 2 21:50 sys drwxrwxrwt 2 root root 4.0K Apr 23 06:28 tmp drwxr-xr-x 12 root root 4.0K Apr 21 11:05 usr drwxr-xr-x 11 root root 4.0K Apr 21 11:05 var lrwxrwxrwx 1 root root 26 Apr 23 06:28 vmlinuz ->=20 boot/vmlinuz-6.12.78-cip19 lrwxrwxrwx 1 root root 26 Apr 23 06:28 vmlinuz.old ->=20 boot/vmlinuz-6.12.78-cip19 ``` Will send a v4 patch with a =E2=80=9CFixes=E2=80=9D tag. That should unbloc= k builds for=20 Bookworm or earlier that mask the systemd service. Many Thanks, Badrikesh On Friday, February 20, 2026 at 1:51:04=E2=80=AFPM UTC+5:30 MOESSBAUER, Fel= ix wrote: > On Thu, 2026-02-19 at 20:10 +0100, Jan Kiszka wrote: > > On 19.02.26 18:52, Jan Kiszka wrote: > > > On 19.02.26 05:44, 'Badrikesh Prusty' via isar-users wrote: > > > > changes in v3: > > > > * Do not disable pre-population of enabled systemd services during= =20 > build, > > > > as this is the correct default behavior. Downstream layers can=20 > disable > > > > it if needed. > > > > * Ignore failures from systemd preset only. > > > >=20 > > > > changes in v2: > > > > * Disable populate-systemd-preset at build time by default due to= =20 > service > > > > failures observed on some systems. > > > >=20 > > > > Badrikesh Prusty (1): > > > > image-postproc: ignore systemd preset failures > > > >=20 > > > > meta/classes-recipe/rootfs.bbclass | 2 +- > > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > >=20 > > >=20 > > > Is this series aiming at these new warnings of Isar? > > >=20 > > > DEBUG: Executing shell function=20 > image_postprocess_disable_systemd_firstboot > > > /proc/ is not mounted. This is not a supported mode of operation.=20 > Please fix > > > your invocation environment to mount /proc/ and /sys/ properly.=20 > Proceeding anyway. > > > Your mileage may vary. > > > Created symlink '/etc/systemd/system/systemd-firstboot.service' =E2= =86=92=20 > '/dev/null'. > > > WARNING: Your image is not configured completely according to=20 > systemd-firstboot. > > > WARNING: It prompted: "" > > > DEBUG: Shell function image_postprocess_disable_systemd_firstboot=20 > finished > > >=20 > >=20 > > Hmm, no. This seems to be another to-do for Felix' rootless patches. I > > was running them, and this warning is gone when going back to vanilla= =20 > Isar. > > Good catch. We need /proc and /sys mounted, which we currently not do > in this task. > > Felix > > >=20 > > Jan > >=20 > > --=20 > > Siemens AG, Foundational Technologies > > Linux Expert Center > > --=20 > Siemens AG > Linux Expert Center > Friedrich-Ludwig-Bauer-Str. 3 > 85748 Garching, Germany > > --=20 You received this message because you are subscribed to the Google Groups "= isar-users" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to isar-users+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/isar-users/= a5997ec4-bc73-4772-80f3-3713a9c788ebn%40googlegroups.com. ------=_Part_631977_1998851439.1777263513097 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi,

Apologies for the delayed response.
It l= ooks like /proc and /sys are already mounted during the beginng of the do_r= ootfs_postprocess task via rootfs_do_mounts function. Shell function run or= der:
```
$ grep "DEBUG: Shell" temp/log.do_rootfs_postp= rocess
DEBUG: Shell function rootfs_do_mounts finished
DEBUG: She= ll function rootfs_do_qemu finished
DEBUG: Shell function image_postpr= ocess_disable_systemd_firstboot finished
DEBUG: Shell function image_p= ostprocess_sshd_key_regen finished
DEBUG: Shell function image_postpro= cess_machine_id finished
DEBUG: Shell function image_postprocess_mark = finished
DEBUG: Shell function image_postprocess_configure finishedDEBUG: Shell function generate_sbom finished
DEBUG: Shell function = rootfs_postprocess_clean_package_cache finished
DEBUG: Shell function = rootfs_postprocess_clean_log_files finished
DEBUG: Shell function root= fs_postprocess_clean_debconf_cache finished
DEBUG: Shell function root= fs_postprocess_clean_pycache finished
DEBUG: Shell function rootfs_pos= tprocess_clean_ldconfig_cache finished
DEBUG: Shell function rootfs_po= stprocess_clean_tmp finished
DEBUG: Shell function rootfs_generate_man= ifest finished
DEBUG: Shell function rootfs_export_dpkg_status finishe= d
DEBUG: Shell function rootfs_cleanup_isar_apt finished
DEBUG: S= hell function image_postprocess_populate_systemd_preset finished
DEBUG= : Shell function image_disable_systemd_networkd finished
DEBUG: Shell = function rootfs_do_umounts finished
```=C2=A0

Added "ls -l" to list the rootfs directories after do_mounts: (/pro= c and /sys mounted)

```
lrwxrwxrwx =C2= =A0 1 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A07 Ma= r =C2=A02 21:50 bin -> usr/bin
drwxr-xr-x =C2=A0 2 root =C2=A0 =C2= =A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 23 06:28 boot
-rwxr-xr-x= =C2=A0 1 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 3.5K Apr 21 1= 1:05 chroot-setup.sh
drwxr-xr-x =C2=A015 root =C2=A0 =C2=A0 =C2=A0 roo= t =C2=A0 =C2=A0 =C2=A0 3.4K Apr 23 06:27 dev
drwxr-xr-x =C2=A058 root = =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 23 06:28 etc
d= rwxr-xr-x =C2=A0 3 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K= Apr 23 06:28 home
lrwxrwxrwx =C2=A0 1 root =C2=A0 =C2=A0 =C2=A0 root = =C2=A0 =C2=A0 =C2=A0 =C2=A0 29 Apr 23 06:28 initrd.img -> boot/initrd.im= g-6.12.78-cip19
lrwxrwxrwx =C2=A0 1 root =C2=A0 =C2=A0 =C2=A0 root =C2= =A0 =C2=A0 =C2=A0 =C2=A0 29 Apr 23 06:28 initrd.img.old -> boot/initrd.i= mg-6.12.78-cip19
drwxr-xr-x =C2=A0 5 industrial industrial 4.0K Apr 21= 11:05 isar-apt
drwxr-xr-x =C2=A011 industrial industrial 4.0K Apr 23 = 06:28 isar-work
lrwxrwxrwx =C2=A0 1 root =C2=A0 =C2=A0 =C2=A0 root =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A07 Mar =C2=A02 21:50 lib -> usr/lib
l= rwxrwxrwx =C2=A0 1 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A09 Mar =C2=A02 21:50 lib64 -> usr/lib64
drwxr-xr-x =C2=A0 = 2 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 21 11:05 med= ia
drwxr-xr-x =C2=A0 2 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 = =C2=A0 4.0K Apr 21 11:05 mnt
drwxr-xr-x =C2=A0 3 root =C2=A0 =C2=A0 = =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 23 06:28 opt
dr-xr-xr-x 813 = root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00 Apr 23 0= 6:28 proc
drwx------ =C2=A0 3 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 = =C2=A0 =C2=A0 4.0K Apr 23 06:28 root
drwxr-xr-x =C2=A0 9 root =C2=A0 = =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 23 06:28 run
lrwxrwxr= wx =C2=A0 1 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A08 Mar =C2=A02 21:50 sbin -> usr/sbin
drwxr-xr-x =C2=A0 2 root = =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 21 11:05 srv
d= rwxr-xr-x =C2=A013 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A00 Mar =C2=A02 21:50 sys
drwxrwxrwt =C2=A0 2 root =C2=A0 =C2= =A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 23 06:28 tmp
drwxr-xr-x = =C2=A012 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 4.0K Apr 21 11= :05 usr
drwxr-xr-x =C2=A011 root =C2=A0 =C2=A0 =C2=A0 root =C2=A0 =C2= =A0 =C2=A0 4.0K Apr 21 11:05 var
lrwxrwxrwx =C2=A0 1 root =C2=A0 =C2= =A0 =C2=A0 root =C2=A0 =C2=A0 =C2=A0 =C2=A0 26 Apr 23 06:28 vmlinuz -> b= oot/vmlinuz-6.12.78-cip19
lrwxrwxrwx =C2=A0 1 root =C2=A0 =C2=A0 =C2= =A0 root =C2=A0 =C2=A0 =C2=A0 =C2=A0 26 Apr 23 06:28 vmlinuz.old -> boot= /vmlinuz-6.12.78-cip19
```

Will send a= v4 patch with a =E2=80=9CFixes=E2=80=9D tag. That should unblock builds fo= r Bookworm or earlier that mask the systemd service.

=
Many Thanks,
Badrikesh

On Friday, February 20, = 2026 at 1:51:04=E2=80=AFPM UTC+5:30 MOESSBAUER, Felix wrote:
On Thu, 2026-02-19 at 20:10= +0100, Jan Kiszka wrote:
> On 19.02.26 18:52, Jan Kiszka wrote:
> > On 19.02.26 05:44, 'Badrikesh Prusty' via isar-users = wrote:
> > > changes in v3:
> > > * Do not disable pre-population of enabled systemd servi= ces during build,
> > > as this is the correct default behavior. Downstream la= yers can disable
> > > it if needed.
> > > * Ignore failures from systemd preset only.
> > >=20
> > > changes in v2:
> > > * Disable populate-systemd-preset at build time by defau= lt due to service
> > > failures observed on some systems.
> > >=20
> > > Badrikesh Prusty (1):
> > > image-postproc: ignore systemd preset failures
> > >=20
> > > meta/classes-recipe/rootfs.bbclass | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >=20
> >=20
> > Is this series aiming at these new warnings of Isar?
> >=20
> > DEBUG: Executing shell function image_postprocess_disable_sys= temd_firstboot
> > /proc/ is not mounted. This is not a supported mode of operat= ion. Please fix
> > your invocation environment to mount /proc/ and /sys/ properl= y. Proceeding anyway.
> > Your mileage may vary.
> > Created symlink '/etc/systemd/system/systemd-firstboot.se= rvice' =E2=86=92 '/dev/null'.
> > WARNING: Your image is not configured completely according to= systemd-firstboot.
> > WARNING: It prompted: ""
> > DEBUG: Shell function image_postprocess_disable_systemd_first= boot finished
> >=20
>=20
> Hmm, no. This seems to be another to-do for Felix' rootless pa= tches. I
> was running them, and this warning is gone when going back to vani= lla Isar.

Good catch. We need /proc and /sys mounted, which we currently not do
in this task.

Felix

>=20
> Jan
>=20
> --=20
> Siemens AG, Foundational Technologies
> Linux Expert Center

--=20
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

--
You received this message because you are subscribed to the Google Groups &= quot;isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to isar-use= rs+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-use= rs/a5997ec4-bc73-4772-80f3-3713a9c788ebn%40googlegroups.com.
------=_Part_631977_1998851439.1777263513097-- ------=_Part_631976_800779142.1777263513097--