From: Jan Kiszka <jan.kiszka@siemens.com>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
akihiro27.suzuki@toshiba.co.jp, isar-users@googlegroups.com,
ch@denx.de
Cc: daniel.sangorrin@toshiba.co.jp, cip-dev@lists.cip-project.org
Subject: Re: debootrap error
Date: Mon, 18 Mar 2019 11:18:54 +0100 [thread overview]
Message-ID: <204e9223-ed2b-9697-38a9-847fe2ee8704@siemens.com> (raw)
In-Reply-To: <24beb970-86d2-c672-08e7-12732f9dd467@siemens.com>
On 18.03.19 11:17, Claudius Heine wrote:
> Hi,,
>
> On 18/03/2019 11.14, akihiro27.suzuki@toshiba.co.jp wrote:
>> Hi,
>>
>>> That's a good hint: Suzuki-san, could you check if binfmt_misc is
>>> available as
>>> kernel feature/module on that machine? There may also be some warning
>>> during the
>>> container startup.
>> I checked it and maybe it is available.
>>
>> $ mount | grep binfmt
>> systemd-1 on /proc/sys/fs/binfmt_misc type autofs
>> (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=18804)
>> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
>> $ lsmod | grep binfmt
>> binfmt_misc 20480 1
>> $ cat /boot/config-4.15.0-46-generic | grep BINFMT
>> CONFIG_BINFMT_ELF=y
>> CONFIG_COMPAT_BINFMT_ELF=y
>> CONFIG_BINFMT_SCRIPT=y
>> CONFIG_BINFMT_MISC=m
>> $ ls /proc/sys/fs/binfmt_misc/
>> python2.7 qemu-armeb qemu-mips64 qemu-ppc64le
>> qemu-sparc status
>> python3.5 qemu-cris qemu-mips64el qemu-riscv32
>> qemu-sparc32plus
>> python3.6 qemu-hppa qemu-mipsel qemu-riscv64 qemu-sparc64
>> qemu-aarch64 qemu-m68k qemu-ppc qemu-s390x qemu-xtensa
>> qemu-alpha qemu-microblaze qemu-ppc64 qemu-sh4 qemu-xtensaeb
>> qemu-arm qemu-mips qemu-ppc64abi32 qemu-sh4eb register
>> $ cat /proc/sys/fs/binfmt_misc/status
>> enabled
>
> That is how my qemu-arm setting looks like. Do you have a different qemu path?
Even if, it shouldn't be after starting the container: We allow it to adjust the
system-wide binfmt configuration (one reason for --privileged).
Jan
>
> $ cat /proc/sys/fs/binfmt_misc/qemu-arm
> enabled
> interpreter /usr/bin/qemu-arm-static
> flags: OCF
> offset 0
> magic 7f454c4601010100000000000000000002002800
> mask ffffffffffffff00fffffffffffffffffeffffff
>
> regards,
> Claudius
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-03-18 10:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HK0PR01MB297958B4B49D80F30DD800D9E24B0@HK0PR01MB2979.apcprd01.prod.exchangelabs.com>
[not found] ` <OSAPR01MB37633BA45B40D16877229C51D04B0@OSAPR01MB3763.jpnprd01.prod.outlook.com>
[not found] ` <375b3b16-8688-6fb2-4d4b-fc130c501c7e@siemens.com>
[not found] ` <TY2PR01MB5146389CBF352FDC6F104262D9440@TY2PR01MB5146.jpnprd01.prod.outlook.com>
[not found] ` <cc3ea2e6-79d9-ed10-f1a3-cf615c3e6ec8@siemens.com>
[not found] ` <TY2PR01MB514615FB285AF43385A49493D9470@TY2PR01MB5146.jpnprd01.prod.outlook.com>
2019-03-18 9:05 ` debootrap error (was: Re: [cip-dev] CIP IRC weekly meeting today) Jan Kiszka
2019-03-18 9:11 ` Claudius Heine
2019-03-18 9:39 ` debootrap error Jan Kiszka
2019-03-18 10:14 ` akihiro27.suzuki
2019-03-18 10:17 ` Claudius Heine
2019-03-18 10:18 ` Jan Kiszka [this message]
2019-03-19 5:18 ` akihiro27.suzuki
2019-03-19 7:22 ` Claudius Heine
2019-03-19 7:51 ` Jan Kiszka
2019-03-19 8:01 ` Claudius Heine
2019-03-19 9:09 ` Jan Kiszka
2019-03-19 9:26 ` Claudius Heine
2019-03-19 9:45 ` Jan Kiszka
2019-03-19 10:14 ` Henning Schild
2019-03-19 10:27 ` 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=204e9223-ed2b-9697-38a9-847fe2ee8704@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=akihiro27.suzuki@toshiba.co.jp \
--cc=ch@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=claudius.heine.ext@siemens.com \
--cc=daniel.sangorrin@toshiba.co.jp \
--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