From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6669654310420217856 X-Received: by 2002:a05:6402:1659:: with SMTP id s25mr2593077edx.2.1552987564143; Tue, 19 Mar 2019 02:26:04 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a50:9fad:: with SMTP id c42ls5060749edf.1.gmail; Tue, 19 Mar 2019 02:26:03 -0700 (PDT) X-Google-Smtp-Source: APXvYqwRJ1uLk+JPfFdxmW+cq0/U61IlTSJuhs3D1XgNmedvgehx5VRslCysj0wYuPt3Eg6zCkUN X-Received: by 2002:a50:aa70:: with SMTP id p45mr2594279edc.6.1552987563744; Tue, 19 Mar 2019 02:26:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552987563; cv=none; d=google.com; s=arc-20160816; b=p01SVwK7WknNoScZSLUML+uKb/FkoE+Ntug8WWvJuoQHRh0aSrI7dgqCDj34rTfIaP qQvSKmXO16mYx/j7llxej0dj4pji0d4T33VswxDRgrf5qvworyhFk2gKNsPRGymRubbP tq033i+5dkVA1pQ8+4ixhPIpz+BcWJ7o7u6TaLo+DS0ItmKC81egdGDsjUM9GC7FKoV2 Nk886Qq5AKM/bFFvMMhJoCqqZZ/QOlyrN4Xbnqtun2yOlc7Z4FA1mg/pGal+VzKTKS+c sPpYwkFlwrTXim67YDw/PzYMWYvkkvRem0UnTus3Ii9bpWutsBGvFPOjxe6TNHRsQeI2 6XdQ== 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=hbv5+0j4HMDVGgLPjq2sVq5nOVJt1AtYUQWYxcCQ46A=; b=uxwVOYfBPsjyXjrDkR7btJiTO7bxgXPOA/lNBEWXwYpMBIpLPmltvko6k6Ap58X0aJ JNupfyzivFrKZSiE/Yi5sM6+qtbDK1s50nkeX62reMNs8x2HLOpvd1xKLeHCGkUy062D CfkGsJOEBjzTd/JowZltOpf2fNMfZs+Y+Slyk00JdDRcO0xYkz/QJh1B8uFrtCEexB29 DXfB0wgQ+Xab1/bMVcicMw8cS46nBw7Ig30t54nkw9rcSPueQ442yXJncwonmtR6lsMz a9CqhIAudmzfbk3BIhBsCK5xshIh88kdWmOkSrCm47KYTOvd+rMGesz6n5X1dP/spSPZ z17Q== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from david.siemens.de (david.siemens.de. [192.35.17.14]) by gmr-mx.google.com with ESMTPS id a7si649971edb.1.2019.03.19.02.26.03 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Mar 2019 02:26:03 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) client-ip=192.35.17.14; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.14 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id x2J9Q2FL027920 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 19 Mar 2019 10:26:02 +0100 Received: from [139.25.69.232] (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x2J9Q1VT027190; Tue, 19 Mar 2019 10:26:01 +0100 Subject: Re: debootrap error To: Jan Kiszka , akihiro27.suzuki@toshiba.co.jp, isar-users@googlegroups.com, ch@denx.de Cc: daniel.sangorrin@toshiba.co.jp, cip-dev@lists.cip-project.org References: <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> <48868c49-3ab2-57f3-2a1e-2a7cf4ff839c@siemens.com> <975512b8-1cf8-a830-29cb-3cd59462135a@siemens.com> <08760c2cbcce3290a6c0c843855b6e8decc668bf.camel@siemens.com> From: Claudius Heine Message-ID: <7c78fe51-6a12-b4d9-8566-8021d21857fe@siemens.com> Date: Tue, 19 Mar 2019 10:26:01 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: kl8Lx0G0E0Qs On 19/03/2019 10.09, Jan Kiszka wrote: > On 19.03.19 09:01, Claudius Heine wrote: >> On Tue, 2019-03-19 at 08:51 +0100, Jan Kiszka wrote: >>> On 19.03.19 08:22, Claudius Heine wrote: >>>> Hi Suzuki-san, >>>> >>>> On 19/03/2019 06.18, akihiro27.suzuki@toshiba.co.jp wrote: >>>>> Hi, >>>>> >>>>>>> That is how my qemu-arm setting looks like. Do you have a >>>>>>> differentqemu path? >>>>>>> >>>>>>> $ cat /proc/sys/fs/binfmt_misc/qemu-arm >>>>>>> enabled >>>>>>> interpreter /usr/bin/qemu-arm-static >>>>>>> flags: OCF >>>>>>> offset 0 >>>>>>> magic 7f454c4601010100000000000000000002002800 >>>>>>> mask ffffffffffffff00fffffffffffffffffeffffff >>>>> My qemu-arm setting is as follows: >>>>> >>>>>       $ cat /proc/sys/fs/binfmt_misc/qemu-arm >>>>>       enabled >>>>>       interpreter /usr/bin/qemu-arm >>>>>       flags: OC >>>>>       offset 0 >>>>>       magic 7f454c4601010100000000000000000002002800 >>>>>       mask ffffffffffffff00fffffffffffffffffeffffff >>>>> >>>>> According to this, the interpreter path was not same. >>>>> My machine used /usr/bin/qemu-arm but Claudius's machine used >>>>> /usr/bin/qemu-arm-static. >>>>> >>>>> If the first place, my machine didn't have /usr/bin/qemu-arm- >>>>> static. >>>>> So, I installed qemu-user-static as follows: >>>>> >>>>>       $ sudo aptitude install qemu-user-static >>>>>       [sudo] password for akihiro: >>>>>       The following NEW packages will be installed: >>>>>         qemu-user-static{b} >>>>>       0 packages upgraded, 1 newly installed, 0 to remove and 0 >>>>> not upgraded. >>>>>       Need to get 10.0 MB of archives. After unpacking 101 MB will >>>>> be used. >>>>>       The following packages have unmet dependencies: >>>>>        qemu-user-static : Conflicts: qemu-user-binfmt but >>>>> 1:2.11+dfsg-1ubuntu7.10 is installed >>>>>        qemu-user-binfmt : Conflicts: qemu-user-static but >>>>> 1:2.11+dfsg-1ubuntu7.10 is to be installed >>>>>       The following actions will resolve these dependencies: >>>>>            Remove the following packages: >>>>>       1)     qemu-user-binfmt [1:2.11+dfsg-1ubuntu7.10 (bionic- >>>>> updates, now)] >>>>>       Accept this solution? [Y/n/q/?] Y >>>>>       The following NEW packages will be installed: >>>>>         qemu-user-static >>>>>       The following packages will be REMOVED: >>>>>         qemu-user-binfmt{a} >>>>>       0 packages upgraded, 1 newly installed, 1 to remove and 0 >>>>> not upgraded. >>>>>       Need to get 10.0 MB of archives. After unpacking 101 MB will >>>>> be used. >>>>>       Do you want to continue? [Y/n/?] Y >>>>>       Get: 1 http://ftp.jaist.ac.jp/pub/Linux/ubuntu bionic- >>>>> updates/universe >>>>> amd64 qemu-user-static amd64 1:2.11+dfsg-1ubuntu7.10 [10.0 MB] >>>>>       Fetched 10.0 MB in 1min 5s (155 kB/s) >>>>>       (Reading database ... 299683 files and directories currently >>>>> installed.) >>>>>       Removing qemu-user-binfmt (1:2.11+dfsg-1ubuntu7.10) ... >>>>>       Selecting previously unselected package qemu-user-static. >>>>>       (Reading database ... 299683 files and directories currently >>>>> installed.) >>>>>       Preparing to unpack >>>>> .../qemu-user-static_1%3a2.11+dfsg-1ubuntu7.10_amd64.deb ... >>>>>       Unpacking qemu-user-static (1:2.11+dfsg-1ubuntu7.10) ... >>>>>       Setting up qemu-user-static (1:2.11+dfsg-1ubuntu7.10) ... >>>>>       Processing triggers for man-db (2.8.3-2ubuntu0.1) ... >>>>> >>>>> After that, I checked my qemu-arm setting. >>>>> The interpreter path has been changed to /usr/bin/qemu-arm-static >>>>> as below: >>>>> >>>>>       $ cat /proc/sys/fs/binfmt_misc/qemu-arm >>>>>       enabled >>>>>       interpreter /usr/bin/qemu-arm-static >>>>>       flags: OC >>>>>       offset 0 >>>>>       magic 7f454c4601010100000000000000000002002800 >>>>>       mask ffffffffffffff00fffffffffffffffffeffffff >>>>> >>>>> After that, I built board-bbb.yml as below, and it succeeded! >>>>> >>>>>       $ ./kas-docker --isar build kas.yml:board-bbb.yml >>>>> >>>>> The root cause of this error is that my machine was not using >>>>> statically linked user mode qemu binaries? >>>> >>>> Well the docker container has the 'qemu-user-static' files >>>> installed as a >>>> dependency of qemu-debootstrap. The dynamic linking version would >>>> not work here, >>>> because qemu-deboostrap will copy just the one binary to the >>>> bootstrapped rootfs >>>> before chrooting into it. The binfmt_misc settings needs to point >>>> to the qemu >>>> static binary that was copied to the rootfs for this to work. The >>>> error of >>>> course is pretty misleading and stumbled over that very often >>>> myself. >>>> >>>> And what your problem shows as well is that the call of 'update- >>>> binfmts >>>> --enable' (which happens in the docker entry point script) does not >>>> seem to fix >>>> the path. >>> >>> ...which is good to know. Maybe it gets tricked by something being >>> enabled >>> already. But I thought I tested this. Anyway, I guess we need to >>> study that >>> script /wrt how to achieve some reliable rewriting of the settings. >> >> Well you could just call '/var/lib/dpkg/info/qemu-user-static.postinst' >> from the docker entry point :) >> > > Ugly... And that call will actually be nop due to how the script works > (if it works at all). Well dpkg-reconfigure would be a bit nicer... Claudius > > It seems this binfmt installation never worked for the isar-kas > container: > > builder@384a365634ab:~$ ls /usr/share/binfmts/ > python2.7  python3.5 > > And python2.7 does a file installation+ an update-binfmt --import - > rather than a --install - during its postinst. > > "For packages, this is preferable to using the --install option, as > a format file can be installed without update-binfmts needing to be > available." > [update-binfmt man page] > > Jan > -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de