From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669654310420217856 X-Received: by 2002:a1c:cf48:: with SMTP id f69mr266589wmg.13.1552991227840; Tue, 19 Mar 2019 03:27:07 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:fc51:: with SMTP id e17ls3945003wrs.15.gmail; Tue, 19 Mar 2019 03:27:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqy6HrfRga0m2hk353kk/iFC9tRjJKCTQ354Ps2cPuzcnVJkUyOkgD42taZDX7Pyau0HfMAf X-Received: by 2002:adf:fa02:: with SMTP id m2mr531800wrr.4.1552991227260; Tue, 19 Mar 2019 03:27:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552991227; cv=none; d=google.com; s=arc-20160816; b=LGO3+SvcDOdU4+hhKoljzOEx0H0OwM11b4QIFaR9Xvr7w/pqf2SKeu028jYnw3x3ib 587N9dM34lHK3zrjca26gmePuX5LUL9CFNQGQcaCJIcIVH8T4nq4866NorksGJ7miF/n DtHMVkB3n4kaB3s+XwzORjAkl0zQqW1st13Eulepcou8HCVQXc18yevqJHTDfsCVaTW7 M2VuMfo0JEGSlBtQROeDEdx7ZyDQuuweUzJ2eJzDHyuEKZHPiQw4ZGjMjuiNt8a4J7pR PDcwNAeW12JGSEcbPVbdDryhyezQCmf2cPPt3SW2uRrbMo+UpTw7ZscmbcLBTBjSkJYT ZxCg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject; bh=mbLpGt/9cLQFGUYtubly65XkxaI9C9vgLSnPRbxvGlk=; b=MQyF5itKpvlzupJNXhm8lUQvtmLbekTxuBG3eqT6Rhzooao1+LHc6D6vzM0RBABwnb 3MtIAt0WKQN80lC1QR340pMqsv317jv25ps7QCWkIrcowL0YRQMc8y7/KZ/rwFf3OtSX FxEd5Ako7jwRg770C41VC0POUcW4AtHG1y9/M8gxbwpneCJ1lpaH2DAsN7jBC+29HBdd nnAh2FuAt8ZtWM24JNV5kadia+b32LXJ5kePB962Ip8Vl/EZEbfHNgXg3u65sbmuadbp lAd2fp4gpO5Yfpl0MYlY4WNg03c/I3eUyd01Gf7aLA1JOXJWlo4/eY1pO9TYRiah22aH eT4A== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from lizzard.sbs.de (lizzard.sbs.de. [194.138.37.39]) by gmr-mx.google.com with ESMTPS id y196si69359wmd.0.2019.03.19.03.27.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Mar 2019 03:27:07 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) client-ip=194.138.37.39; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.39 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id x2JAR535022576 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 19 Mar 2019 11:27:06 +0100 Received: from [139.22.45.157] ([139.22.45.157]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x2JAR4D7011229; Tue, 19 Mar 2019 11:27:04 +0100 Subject: Re: debootrap error To: Henning Schild Cc: Claudius Heine , akihiro27.suzuki@toshiba.co.jp, isar-users@googlegroups.com, ch@denx.de, daniel.sangorrin@toshiba.co.jp, cip-dev@lists.cip-project.org 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> From: Jan Kiszka Message-ID: <28733da6-84da-4b28-a92f-1586179c05e4@siemens.com> Date: Tue, 19 Mar 2019 11:27:04 +0100 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: <20190319111434.104d1362@md1za8fc.ad001.siemens.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: X4b8npOo7NgP 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@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