All of lore.kernel.org
 help / color / mirror / Atom feed
From: jan.kiszka@siemens.com (Jan Kiszka)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] debootrap error
Date: Tue, 19 Mar 2019 11:27:04 +0100	[thread overview]
Message-ID: <28733da6-84da-4b28-a92f-1586179c05e4@siemens.com> (raw)
In-Reply-To: <20190319111434.104d1362@md1za8fc.ad001.siemens.net>

On 19.03.19 11:14, Henning Schild wrote:
> Am Mon, 18 Mar 2019 11:18:54 +0100
> schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
> 
>> 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

  reply	other threads:[~2019-03-19 10:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14  1:55 [cip-dev] CIP IRC weekly meeting today SZ Lin (林上智)
2019-03-14  4:38 ` Nobuhiro Iwamatsu
2019-03-14  7:26 ` daniel.sangorrin at toshiba.co.jp
2019-03-14  9:19   ` Chris Paterson
2019-03-14  9:23   ` Patryk Mungai Ndungu
2019-03-15  9:24   ` Jan Kiszka
2019-03-15  9:48     ` akihiro27.suzuki at toshiba.co.jp
2019-03-15 10:50       ` Jan Kiszka
2019-03-18  1:42         ` akihiro27.suzuki at toshiba.co.jp
2019-03-18  9:05           ` [cip-dev] debootrap error (was: Re: CIP IRC weekly meeting today) Jan Kiszka
2019-03-18  9:11             ` Claudius Heine
2019-03-18  9:39               ` [cip-dev] debootrap error Jan Kiszka
2019-03-18 10:14                 ` akihiro27.suzuki at toshiba.co.jp
2019-03-18 10:17                   ` Claudius Heine
2019-03-18 10:18                     ` Jan Kiszka
2019-03-19  5:18                       ` akihiro27.suzuki at toshiba.co.jp
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 [this message]
2019-03-18  2:53         ` [cip-dev] CIP IRC weekly meeting today akihiro27.suzuki at toshiba.co.jp
2019-03-18  8:56           ` [cip-dev] debootstrap error (was: Re: CIP IRC weekly meeting today) Jan Kiszka
2019-03-18  8:59             ` akihiro27.suzuki at toshiba.co.jp
2019-03-18  8:42     ` [cip-dev] CIP IRC weekly meeting today Christian Storm
2019-03-18  9:14       ` akihiro27.suzuki at toshiba.co.jp
2019-03-18 10:27         ` Christian Storm
2019-03-22  5:01           ` akihiro27.suzuki at toshiba.co.jp
2019-03-22 12:37             ` Christian Storm
2019-03-27  8:25               ` akihiro27.suzuki at toshiba.co.jp
2019-03-29 13:21                 ` Christian Storm
2019-04-01  2:48                   ` akihiro27.suzuki at toshiba.co.jp
2019-04-01  6:48                     ` Christian Storm
2019-04-02  3:50                       ` akihiro27.suzuki at toshiba.co.jp
2019-04-02  6:45                         ` Christian Storm
2019-04-02  8:14                           ` akihiro27.suzuki at toshiba.co.jp
2019-04-26 10:34                           ` akihiro27.suzuki at toshiba.co.jp

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=28733da6-84da-4b28-a92f-1586179c05e4@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.