From mboxrd@z Thu Jan 1 00:00:00 1970 From: jan.kiszka@siemens.com (Jan Kiszka) Date: Tue, 19 Mar 2019 11:27:04 +0100 Subject: [cip-dev] debootrap error In-Reply-To: <20190319111434.104d1362@md1za8fc.ad001.siemens.net> References: <375b3b16-8688-6fb2-4d4b-fc130c501c7e@siemens.com> <02844bd9-fe8d-199f-27e3-42f59bb64163@siemens.com> <41b9fdc25373948d08ad360dc1db13340648cc93.camel@siemens.com> <1d4da986-92e6-87e3-11a4-30e15b48359d@siemens.com> <24beb970-86d2-c672-08e7-12732f9dd467@siemens.com> <204e9223-ed2b-9697-38a9-847fe2ee8704@siemens.com> <20190319111434.104d1362@md1za8fc.ad001.siemens.net> Message-ID: <28733da6-84da-4b28-a92f-1586179c05e4@siemens.com> To: cip-dev@lists.cip-project.org List-Id: cip-dev.lists.cip-project.org On 19.03.19 11:14, Henning Schild wrote: > Am Mon, 18 Mar 2019 11:18:54 +0100 > schrieb "[ext] Jan Kiszka" : > >> On 18.03.19 11:17, Claudius Heine wrote: >>> Hi,, >>> >>> On 18/03/2019 11.14, akihiro27.suzuki at 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). > > We really need a kernel patch for a binfmt cgroup/namespace. > I don't disagree. I have no idea how much effort that would mean. Maybe it's worth asking around on LKML for suggestions. In any case, it will take 2 year - at least - to have that available in all major distros. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux