public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jonas Reindl <jonas.reindl@kilobaser.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: Rapios Wic Image
Date: Mon, 14 Mar 2022 14:59:15 +0100	[thread overview]
Message-ID: <d1200f40-3cb7-00d3-cece-478c3aa69712@kilobaser.com> (raw)
In-Reply-To: <20220310090422.23b8e7ee@md1za8fc.ad001.siemens.net>

[-- Attachment #1: Type: text/plain, Size: 3008 bytes --]


On 3/10/22 09:04, Henning Schild wrote:
> Hey Jonas,
>
> Am Wed, 9 Mar 2022 19:57:02 +0100
> schrieb Jonas Reindl<jonas.reindl@kilobaser.com>:
>
>> Hey everyone,
>>
>> I'm currently trying to build a raspios image as "wic-img" and get a
>> python import error.
>>
>> kas-version: 3.0.2
>>
>> isar-version: 0.8
> You might in fact want to try "next" instead. Isar master and releases
> are often slow to move, maybe your issue is fixed already.

First of all thanks for the help.

Upgrading to next didn't had a direct impact on the install. The 
suggestion from Jan Kiszka with

WIC_IMAGER_INSTALL += "python3-distutils"

helped to get the wic imager to start. But now I'm stuck with the problem, that wic is looking for the kernel in /boot/vmlinux.
Raspios installs the kernel with kernel.img. So I assumend I would need to set
IMAGE_BOOT_FILES = " \
      /kernel.img;vmlinuz \
      "

to remap the kernel. This still ends in the error message:

ERROR: kernel /build/tmp/work/raspios-bullseye-armhf/myimage-image-base-rpi-arm-wic-img/1.0-r0/rootfs/boot/vmlinux not found

Would you have any ideas to get that working.

>   
>> I'm using kas-container to build the images with multiconfig for that.
>>
>> ```
>>
>>       MACHINE ?= "rpi-arm"
>>       DISTRO ?= "raspios-bullseye"
>>
>>       IMAGE_FSTYPES = "wic-img"
>>
>> ```
>>
>> Error:
>>
>> Exception: bb.process.ExecutionError: Execution of
>> '/build/tmp/work/raspios-bullseye-armhf/my-image-base-rpi-arm-wic-img/1.0-r0/temp/run.generate_wic_image.285'
>> failed with exit code 1:
>> Traceback (most recent call last):
>>     File "/work/layers/isar/scripts/wic", line 27, in <module>
>>       from distutils import spawn
>> ImportError: cannot import name 'spawn' from 'distutils'
>> (/usr/lib/python3.9/distutils/__init__.py)
>> WARNING: exit code 1 from a shell command.
>>
>> If I enter the build environment with the kas shell and execute
>> python3 I'm able to import spawn. I also rebuild the docker container
>> to explicitly include python3-distutils. Maybe I misunderstood
>> something, but I don't know how I should further debug that.
> In fact wic is not executed in that container, but in a chroot in there.
>
> I think we currently lack a wic raspi example in isar itself, maybe
> there is something broken indeed. But it is possible and wic will be
> much better than "rpi-sdimg" which is currently questioned a lot and
> also might be broken at the moment.
>
> https://github.com/siemens/jailhouse-images

I tried to follow the wic configuration as good as possible from the jailhouse-image, but jailhouse uses native debian, which will install

the kernel differently as raspios does. Changing to debian native is not possible for me as I need that image to be able to boot on different raspberries.


>
> has rpi4 with wic in it
>
> regards,
> Henning
>   
>> In case needed I can provide the fullstack trace and the sh script
>> which tried to generate the wic.
>>
>> Best regards,
>>
>> Jonas
>>
>>
>>
BR,

Jonas

[-- Attachment #2: Type: text/html, Size: 4487 bytes --]

  reply	other threads:[~2022-03-14 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-09 18:57 Jonas Reindl
2022-03-10  7:30 ` Jan Kiszka
2022-03-10  8:04 ` Henning Schild
2022-03-14 13:59   ` Jonas Reindl [this message]
2022-03-14 14:58     ` Jan Kiszka

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=d1200f40-3cb7-00d3-cece-478c3aa69712@kilobaser.com \
    --to=jonas.reindl@kilobaser.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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