From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669654310420217856 X-Received: by 2002:a7b:cf23:: with SMTP id m3mr229213wmg.21.1552990478223; Tue, 19 Mar 2019 03:14:38 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:adf:e2d1:: with SMTP id d17ls1524608wrj.8.gmail; Tue, 19 Mar 2019 03:14:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqxwJDwXhNTnqGFNkcw1eIHT8CwpXn/oI+NxHWJmaSjpguyqcLPsX/bTyUhNurwJhlm1jMAi X-Received: by 2002:adf:eb88:: with SMTP id t8mr1045543wrn.16.1552990477681; Tue, 19 Mar 2019 03:14:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552990477; cv=none; d=google.com; s=arc-20160816; b=mRQTk3tO8cO5X5ylh5eZUY+zyZosVF8s5jlG99eUpAvC33kAFg1uzOi3XKr40XdyS5 kWij8MMP/8cwXh4dNYD+ZhfBklbecpOlwenS5BTCvuqsF6TqKewkSsm1F6P5UmcxxqzA EJBbv5Cov/wunbDCGU8Fz95Wl9AT+xvGCU9LKN6k+mt1HcKdOXWMPcBAxuF4n5QNWt6U bJJkJbRrvETKyO5yGk3XWozkC5FoHLKO/R7FVNl/+eNkRnK4Sq8DLvBekCfGi2NjV53K 2MtIyGum2OVOT07rY80NbRgVutpRgxQreIpBrKy0UgoUxk8eQuZoQld6zqOD5TxIGoP9 kQJA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date; bh=gByzOH878lvrVUU0XBLBOj4tjYap1nGspseu3q8Ggjw=; b=Ggkb79XEXy7OXVSq2cSdzzNLMQRquIEw/YdjQ6+GZTvoTNauaIejouwcA9FqYLX3WG dwru5Jiyw7ViRLscgIrxLw51fI8sm4PInWiHTKL4iVrG6MRJ/ToNDzWGj19PTXPtPfJi a/LI1/aRcTs1oSU5RqRS4tYg/RxzjI0MTUiB2QHe11a2M7/PafoJ6lzDVMgYCv3TnQjt ULoGPGrRNShz0Lpt2GHOOXcHhmLvD+BaDp9x869hSTWRFO8tGJ9FMj9cTxGwYWYQwMUN fWCIH/QeMhp2wyvuUbeKvO06NqdoMQZWOPo0ffT5i1oQiaJT3KwrWLcnuZTtAb0lHTrO VIXg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Return-Path: Received: from goliath.siemens.de (goliath.siemens.de. [192.35.17.28]) by gmr-mx.google.com with ESMTPS id q6si112950wmf.4.2019.03.19.03.14.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Mar 2019 03:14:37 -0700 (PDT) Received-SPF: pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) client-ip=192.35.17.28; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of henning.schild@siemens.com designates 192.35.17.28 as permitted sender) smtp.mailfrom=henning.schild@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by goliath.siemens.de (8.15.2/8.15.2) with ESMTPS id x2JAEZh4008352 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 19 Mar 2019 11:14:35 +0100 Received: from md1za8fc.ad001.siemens.net ([139.25.69.122]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x2JAEYb3007308; Tue, 19 Mar 2019 11:14:34 +0100 Date: Tue, 19 Mar 2019 11:14:34 +0100 From: Henning Schild To: "[ext] Jan Kiszka" Cc: Claudius Heine , , , , , Subject: Re: debootrap error Message-ID: <20190319111434.104d1362@md1za8fc.ad001.siemens.net> In-Reply-To: <204e9223-ed2b-9697-38a9-847fe2ee8704@siemens.com> 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> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-TUID: nqOUS0aZIaUy Am Mon, 18 Mar 2019 11:18:54 +0100 schrieb "[ext] Jan Kiszka" : > On 18.03.19 11:17, Claudius Heine wrote: > > Hi,, > >=20 > > On 18/03/2019 11.14, akihiro27.suzuki@toshiba.co.jp wrote: =20 > >> Hi, > >> =20 > >>> 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. =20 > >> I checked it and maybe it is available. > >> > >> =C2=A0=C2=A0=C2=A0=C2=A0 $ mount | grep binfmt > >> =C2=A0=C2=A0=C2=A0=C2=A0 systemd-1 on /proc/sys/fs/binfmt_misc type au= tofs=20 > >> (rw,relatime,fd=3D31,pgrp=3D1,timeout=3D0,minproto=3D5,maxproto=3D5,di= rect,pipe_ino=3D18804) > >> =C2=A0=C2=A0=C2=A0=C2=A0 binfmt_misc on /proc/sys/fs/binfmt_misc type = binfmt_misc > >> (rw,relatime) $ lsmod | grep binfmt > >> =C2=A0=C2=A0=C2=A0=C2=A0 binfmt_misc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 20480=C2=A0 1 > >> =C2=A0=C2=A0=C2=A0=C2=A0 $ cat /boot/config-4.15.0-46-generic=C2=A0 | = grep BINFMT > >> =C2=A0=C2=A0=C2=A0=C2=A0 CONFIG_BINFMT_ELF=3Dy > >> =C2=A0=C2=A0=C2=A0=C2=A0 CONFIG_COMPAT_BINFMT_ELF=3Dy > >> =C2=A0=C2=A0=C2=A0=C2=A0 CONFIG_BINFMT_SCRIPT=3Dy > >> =C2=A0=C2=A0=C2=A0=C2=A0 CONFIG_BINFMT_MISC=3Dm > >> =C2=A0=C2=A0=C2=A0=C2=A0 $ ls /proc/sys/fs/binfmt_misc/ > >> =C2=A0=C2=A0=C2=A0=C2=A0 python2.7=C2=A0=C2=A0=C2=A0=C2=A0 qemu-armeb= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 qemu-mips64=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 qemu-ppc64le =20 > >> qemu-sparc=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 status > >> =C2=A0=C2=A0=C2=A0=C2=A0 python3.5=C2=A0=C2=A0=C2=A0=C2=A0 qemu-cris= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 qemu-mips64el=C2=A0=C2=A0=C2=A0 = qemu-riscv32 =20 > >> qemu-sparc32plus > >> =C2=A0=C2=A0=C2=A0=C2=A0 python3.6=C2=A0=C2=A0=C2=A0=C2=A0 qemu-hppa= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 qemu-mipsel=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 qemu-riscv64 > >> qemu-sparc64 qemu-aarch64=C2=A0 qemu-m68k=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 qemu-ppc > >> qemu-s390x=C2=A0=C2=A0=C2=A0 qemu-xtensa qemu-alpha=C2=A0=C2=A0=C2=A0 = qemu-microblaze > >> qemu-ppc64=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 qemu-sh4=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 qemu-xtensaeb qemu-arm > >> qemu-mips=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 qemu-ppc64abi32=C2= =A0 qemu-sh4eb=C2=A0=C2=A0=C2=A0 register $ > >> cat /proc/sys/fs/binfmt_misc/status enabled =20 > >=20 > > That is how my qemu-arm setting looks like. Do you have a different > > qemu path? =20 >=20 > 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. Henning > Jan >=20 > >=20 > > $ cat /proc/sys/fs/binfmt_misc/qemu-arm > > enabled > > interpreter /usr/bin/qemu-arm-static > > flags: OCF > > offset 0 > > magic 7f454c4601010100000000000000000002002800 > > mask ffffffffffffff00fffffffffffffffffeffffff > >=20 > > regards, > > Claudius =20 >=20