On 22.11.21 07:30, Jan Kiszka wrote:
> On 22.11.21 00:56, [email protected] wrote:
>> Dear Jan,
>>
>> I've tried to build RaspPI4 with next branch.
>>
>> This is the log error for
>> ./build/tmp/work/jailhouse-demo-arm64/isar-bootstrap-target/1.0-r0/rootfs/debootstrap/debootstrap.log:
>>
>> Resolving deb.debian.org (deb.debian.org)... 146.75.62.132,
>> 2a04:4e42:7f::644
>> Connecting to deb.debian.org (deb.debian.org)|146.75.62.132|:80...
>> connected.
>> HTTP request sent, awaiting response... 200 OK
>> Length: 87944 (86K) [application/x-debian-package]
>> Saving to:
>> ‘/build/tmp/work/jailhouse-demo-arm64/isar-bootstrap-target/1.0-r0/rootfs//var/cache/apt/archives/partial/zlib1g_1%3a1.2.11.dfsg-2_arm64.deb’
>>
>>      0K .......... .......... .......... .......... .......... 58% 7.94M 0s
>>     50K .......... .......... .......... .....                100%
>> 2.54M=0.02s
>>
>> 2021-11-21 23:51:22 (4.21 MB/s) -
>> ‘/build/tmp/work/jailhouse-demo-arm64/isar-bootstrap-target/1.0-r0/rootfs//var/cache/apt/archives/partial/zlib1g_1%3a1.2.11.dfsg-2_arm64.deb’
>> saved [87944/87944]
>>
>> *chroot: failed to run command ‘/bin/true’: No such file or directory*
>>
> 
> Looks like as if the build started as non-Isar build. Could you provide
> the full log of the console? You can reproduce this by simply calling
> "./kas-container -d build" which will rebuild the previously selection
> menu options, now with debug output.
> 

You sent:

> This is the full log by running "./kas-container -d build":
> 
> + mkdir -p /root/jailhouse-images
> + mkdir -p /root/jailhouse-images/build
> + docker run -v /root/jailhouse-images:/repo:ro -v 
> /root/jailhouse-images:/work:rw -e KAS_WORK_DIR=/work -v 
> /root/jailhouse-images/build:/build:rw --workdir=/repo -e 
> KAS_BUILD_DIR=/build -e USER_ID=1000 -e GROUP_ID=1000 --rm -t -i -e 
> TERM=xterm-256color -e SHELL=/bin/bash --privileged 
> ghcr.io/siemens/kas/kas-isar:2.6.2 -d build
> 2021-11-22 10:47:59 - INFO     - kas 2.6.2 started

That looks fine. What may also cause the issue is qemu-user-static being
installed on the host distro, preventing the required configuration in
the container. See https://github.com/siemens/meta-iot2050/issues/219
for a similar report on another Isar layer.

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/69a90870-65c5-ae42-0467-84526a1a45ee%40siemens.com.

Reply via email to