* debootrap error (was: Re: [cip-dev] CIP IRC weekly meeting today) [not found] ` <TY2PR01MB514615FB285AF43385A49493D9470@TY2PR01MB5146.jpnprd01.prod.outlook.com> @ 2019-03-18 9:05 ` Jan Kiszka 2019-03-18 9:11 ` Claudius Heine 0 siblings, 1 reply; 15+ messages in thread From: Jan Kiszka @ 2019-03-18 9:05 UTC (permalink / raw) To: akihiro27.suzuki, isar-users, Claudius Heine; +Cc: daniel.sangorrin, cip-dev On 18.03.19 02:42, akihiro27.suzuki@toshiba.co.jp wrote: > Hi Jan, > >> Were you building natively on Debian or inside the kas container? > I was executing following commands according to the README.md at isar-cip-core, > so I think I was building inside the kas container. > > $ wget https://raw.githubusercontent.com/siemens/kas/master/kas-docker > $ chmod a+x kas-docker > $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml > > The error is as follows (from log.do_bootstrap of isar-bootstrap-target): > > DEBUG: Executing shell function do_bootstrap > I: Running command: debootstrap --arch armhf --foreign --verbose --variant=minbase --include=locales --components=main,contrib,non-free stretch /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/rootfs http://ftp.de.debian.org/debian > I: Retrieving InRelease > I: Retrieving Release > I: Retrieving Release.gpg > I: Checking Release signature > I: Valid Release signature (key id 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500) > I: Retrieving Packages > I: Validating Packages > I: Retrieving Packages > I: Validating Packages > I: Retrieving Packages > I: Validating Packages > I: Resolving dependencies of required packages... > I: Resolving dependencies of base packages... > I: Found additional required dependencies: libaudit1 libaudit-common libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 libgpg-error0 liblz4-1 libncursesw5 libsemanage1 libsemanage-common libsystemd0 libudev1 libustr-1.0-1 > I: Found additional base dependencies: adduser debian-archive-keyring gpgv libapt-pkg5.0 libc-l10n libstdc++6 > I: Checking component main on http://ftp.de.debian.org/debian... > I: Retrieving libacl1 2.2.52-3+b1 > I: Validating libacl1 2.2.52-3+b1 > I: Retrieving adduser 3.115 > I: Validating adduser 3.115 > I: Retrieving apt 1.4.9 > I: Validating apt 1.4.9 > I: Retrieving libapt-pkg5.0 1.4.9 > I: Validating libapt-pkg5.0 1.4.9 > I: Retrieving libattr1 1:2.4.47-2+b2 > I: Validating libattr1 1:2.4.47-2+b2 > I: Retrieving libaudit-common 1:2.6.7-2 > I: Validating libaudit-common 1:2.6.7-2 > I: Retrieving libaudit1 1:2.6.7-2 > I: Validating libaudit1 1:2.6.7-2 > I: Retrieving base-files 9.9+deb9u8 > I: Validating base-files 9.9+deb9u8 > I: Retrieving base-passwd 3.5.43 > I: Validating base-passwd 3.5.43 > I: Retrieving bash 4.4-5 > I: Validating bash 4.4-5 > I: Retrieving libbz2-1.0 1.0.6-8.1 > I: Validating libbz2-1.0 1.0.6-8.1 > I: Retrieving libdebconfclient0 0.227 > I: Validating libdebconfclient0 0.227 > I: Retrieving coreutils 8.26-3 > I: Validating coreutils 8.26-3 > I: Retrieving dash 0.5.8-2.4 > I: Validating dash 0.5.8-2.4 > I: Retrieving libdb5.3 5.3.28-12+deb9u1 > I: Validating libdb5.3 5.3.28-12+deb9u1 > I: Retrieving debconf 1.5.61 > I: Validating debconf 1.5.61 > I: Retrieving debian-archive-keyring 2017.5 > I: Validating debian-archive-keyring 2017.5 > I: Retrieving debianutils 4.8.1.1 > I: Validating debianutils 4.8.1.1 > I: Retrieving diffutils 1:3.5-3 > I: Validating diffutils 1:3.5-3 > I: Retrieving dpkg 1.18.25 > I: Validating dpkg 1.18.25 > I: Retrieving e2fslibs 1.43.4-2 > I: Validating e2fslibs 1.43.4-2 > I: Retrieving e2fsprogs 1.43.4-2 > I: Validating e2fsprogs 1.43.4-2 > I: Retrieving libcomerr2 1.43.4-2 > I: Validating libcomerr2 1.43.4-2 > I: Retrieving libss2 1.43.4-2 > I: Validating libss2 1.43.4-2 > I: Retrieving findutils 4.6.0+git+20161106-2 > I: Validating findutils 4.6.0+git+20161106-2 > I: Retrieving gcc-6-base 6.3.0-18+deb9u1 > I: Validating gcc-6-base 6.3.0-18+deb9u1 > I: Retrieving libgcc1 1:6.3.0-18+deb9u1 > I: Validating libgcc1 1:6.3.0-18+deb9u1 > I: Retrieving libstdc++6 6.3.0-18+deb9u1 > I: Validating libstdc++6 6.3.0-18+deb9u1 > I: Retrieving libc-bin 2.24-11+deb9u4 > I: Validating libc-bin 2.24-11+deb9u4 > I: Retrieving libc-l10n 2.24-11+deb9u4 > I: Validating libc-l10n 2.24-11+deb9u4 > I: Retrieving libc6 2.24-11+deb9u4 > I: Validating libc6 2.24-11+deb9u4 > I: Retrieving locales 2.24-11+deb9u4 > I: Validating locales 2.24-11+deb9u4 > I: Retrieving multiarch-support 2.24-11+deb9u4 > I: Validating multiarch-support 2.24-11+deb9u4 > I: Retrieving gpgv 2.1.18-8~deb9u4 > I: Validating gpgv 2.1.18-8~deb9u4 > I: Retrieving grep 2.27-2 > I: Validating grep 2.27-2 > I: Retrieving gzip 1.6-5+b1 > I: Validating gzip 1.6-5+b1 > I: Retrieving hostname 3.18+b1 > I: Validating hostname 3.18+b1 > I: Retrieving init-system-helpers 1.48 > I: Validating init-system-helpers 1.48 > I: Retrieving libcap-ng0 0.7.7-3+b1 > I: Validating libcap-ng0 0.7.7-3+b1 > I: Retrieving libgcrypt20 1.7.6-2+deb9u3 > I: Validating libgcrypt20 1.7.6-2+deb9u3 > I: Retrieving libgpg-error0 1.26-2 > I: Validating libgpg-error0 1.26-2 > I: Retrieving libselinux1 2.6-3+b3 > I: Validating libselinux1 2.6-3+b3 > I: Retrieving libsemanage-common 2.6-2 > I: Validating libsemanage-common 2.6-2 > I: Retrieving libsemanage1 2.6-2 > I: Validating libsemanage1 2.6-2 > I: Retrieving libsepol1 2.6-2 > I: Validating libsepol1 2.6-2 > I: Retrieving lsb-base 9.20161125 > I: Validating lsb-base 9.20161125 > I: Retrieving liblz4-1 0.0~r131-2+b1 > I: Validating liblz4-1 0.0~r131-2+b1 > I: Retrieving mawk 1.3.3-17+b3 > I: Validating mawk 1.3.3-17+b3 > I: Retrieving libncursesw5 6.0+20161126-1+deb9u2 > I: Validating libncursesw5 6.0+20161126-1+deb9u2 > I: Retrieving libtinfo5 6.0+20161126-1+deb9u2 > I: Validating libtinfo5 6.0+20161126-1+deb9u2 > I: Retrieving ncurses-base 6.0+20161126-1+deb9u2 > I: Validating ncurses-base 6.0+20161126-1+deb9u2 > I: Retrieving ncurses-bin 6.0+20161126-1+deb9u2 > I: Validating ncurses-bin 6.0+20161126-1+deb9u2 > I: Retrieving libpam-modules 1.1.8-3.6 > I: Validating libpam-modules 1.1.8-3.6 > I: Retrieving libpam-modules-bin 1.1.8-3.6 > I: Validating libpam-modules-bin 1.1.8-3.6 > I: Retrieving libpam-runtime 1.1.8-3.6 > I: Validating libpam-runtime 1.1.8-3.6 > I: Retrieving libpam0g 1.1.8-3.6 > I: Validating libpam0g 1.1.8-3.6 > I: Retrieving libpcre3 2:8.39-3 > I: Validating libpcre3 2:8.39-3 > I: Retrieving perl-base 5.24.1-3+deb9u5 > I: Validating perl-base 5.24.1-3+deb9u5 > I: Retrieving sed 4.4-1 > I: Validating sed 4.4-1 > I: Retrieving sensible-utils 0.0.9+deb9u1 > I: Validating sensible-utils 0.0.9+deb9u1 > I: Retrieving login 1:4.4-4.1 > I: Validating login 1:4.4-4.1 > I: Retrieving passwd 1:4.4-4.1 > I: Validating passwd 1:4.4-4.1 > I: Retrieving libsystemd0 232-25+deb9u8 > I: Validating libsystemd0 232-25+deb9u8 > I: Retrieving libudev1 232-25+deb9u8 > I: Validating libudev1 232-25+deb9u8 > I: Retrieving sysvinit-utils 2.88dsf-59.9 > I: Validating sysvinit-utils 2.88dsf-59.9 > I: Retrieving tar 1.29b-1.1 > I: Validating tar 1.29b-1.1 > I: Retrieving tzdata 2018i-0+deb9u1 > I: Validating tzdata 2018i-0+deb9u1 > I: Retrieving libustr-1.0-1 1.0.4-6 > I: Validating libustr-1.0-1 1.0.4-6 > I: Retrieving bsdutils 1:2.29.2-1+deb9u1 > I: Validating bsdutils 1:2.29.2-1+deb9u1 > I: Retrieving libblkid1 2.29.2-1+deb9u1 > I: Validating libblkid1 2.29.2-1+deb9u1 > I: Retrieving libfdisk1 2.29.2-1+deb9u1 > I: Validating libfdisk1 2.29.2-1+deb9u1 > I: Retrieving libmount1 2.29.2-1+deb9u1 > I: Validating libmount1 2.29.2-1+deb9u1 > I: Retrieving libsmartcols1 2.29.2-1+deb9u1 > I: Validating libsmartcols1 2.29.2-1+deb9u1 > I: Retrieving libuuid1 2.29.2-1+deb9u1 > I: Validating libuuid1 2.29.2-1+deb9u1 > I: Retrieving mount 2.29.2-1+deb9u1 > I: Validating mount 2.29.2-1+deb9u1 > I: Retrieving util-linux 2.29.2-1+deb9u1 > I: Validating util-linux 2.29.2-1+deb9u1 > I: Retrieving liblzma5 5.2.2-1.2+b1 > I: Validating liblzma5 5.2.2-1.2+b1 > I: Retrieving zlib1g 1:1.2.8.dfsg-5 > I: Validating zlib1g 1:1.2.8.dfsg-5 > I: Chosen extractor for .deb packages: dpkg-deb > I: Extracting libacl1... > I: Extracting libattr1... > I: Extracting libaudit-common... > I: Extracting libaudit1... > I: Extracting base-files... > I: Extracting base-passwd... > I: Extracting bash... > I: Extracting libbz2-1.0... > I: Extracting libdebconfclient0... > I: Extracting coreutils... > I: Extracting dash... > I: Extracting libdb5.3... > I: Extracting debconf... > I: Extracting debianutils... > I: Extracting diffutils... > I: Extracting dpkg... > I: Extracting e2fslibs... > I: Extracting e2fsprogs... > I: Extracting libcomerr2... > I: Extracting libss2... > I: Extracting findutils... > I: Extracting gcc-6-base... > I: Extracting libgcc1... > I: Extracting libc-bin... > I: Extracting libc6... > I: Extracting multiarch-support... > I: Extracting grep... > I: Extracting gzip... > I: Extracting hostname... > I: Extracting init-system-helpers... > I: Extracting libcap-ng0... > I: Extracting libgcrypt20... > I: Extracting libgpg-error0... > I: Extracting libselinux1... > I: Extracting libsemanage-common... > I: Extracting libsemanage1... > I: Extracting libsepol1... > I: Extracting lsb-base... > I: Extracting liblz4-1... > I: Extracting mawk... > I: Extracting libncursesw5... > I: Extracting libtinfo5... > I: Extracting ncurses-base... > I: Extracting ncurses-bin... > I: Extracting libpam-modules... > I: Extracting libpam-modules-bin... > I: Extracting libpam-runtime... > I: Extracting libpam0g... > I: Extracting libpcre3... > I: Extracting perl-base... > I: Extracting sed... > I: Extracting sensible-utils... > I: Extracting login... > I: Extracting passwd... > I: Extracting libsystemd0... > I: Extracting libudev1... > I: Extracting sysvinit-utils... > I: Extracting tar... > I: Extracting tzdata... > I: Extracting libustr-1.0-1... > I: Extracting bsdutils... > I: Extracting libblkid1... > I: Extracting libfdisk1... > I: Extracting libmount1... > I: Extracting libsmartcols1... > I: Extracting libuuid1... > I: Extracting mount... > I: Extracting util-linux... > I: Extracting liblzma5... > I: Extracting zlib1g... > I: Running command: chroot /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/rootfs /debootstrap/debootstrap --second-stage > chroot: failed to run command ‘/debootstrap/debootstrap’: No such file or directory > WARNING: exit code 127 from a shell command. > ERROR: Function failed: do_bootstrap (log file is located at /work/build/tmp/work/cip-core-armhf/isar-bootstrap-target/temp/log.do_bootstrap.316) > Looping in isar-users and Claudius. I've no idea why debootstrap should stumble here, apparently over its own feet. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error (was: Re: [cip-dev] CIP IRC weekly meeting today) 2019-03-18 9:05 ` debootrap error (was: Re: [cip-dev] CIP IRC weekly meeting today) Jan Kiszka @ 2019-03-18 9:11 ` Claudius Heine 2019-03-18 9:39 ` debootrap error Jan Kiszka 0 siblings, 1 reply; 15+ messages in thread From: Claudius Heine @ 2019-03-18 9:11 UTC (permalink / raw) To: [ext] Jan Kiszka, akihiro27.suzuki, isar-users, Claudius Heine Cc: daniel.sangorrin, cip-dev Hi, On Mon, 2019-03-18 at 10:05 +0100, [ext] Jan Kiszka wrote: > On 18.03.19 02:42, akihiro27.suzuki@toshiba.co.jp wrote: > > Hi Jan, > > > > > Were you building natively on Debian or inside the kas container? > > I was executing following commands according to the README.md at > > isar-cip-core, > > so I think I was building inside the kas container. > > > > $ wget > > https://raw.githubusercontent.com/siemens/kas/master/kas-docker > > $ chmod a+x kas-docker > > $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml > > > > The error is as follows (from log.do_bootstrap of isar-bootstrap- > > target): > > > > DEBUG: Executing shell function do_bootstrap > > I: Running command: debootstrap --arch armhf --foreign -- > > verbose --variant=minbase --include=locales -- > > components=main,contrib,non-free stretch /work/build/tmp/work/cip- > > core-armhf/isar-bootstrap-target/rootfs > > http://ftp.de.debian.org/debian > > I: Retrieving InRelease > > I: Retrieving Release > > I: Retrieving Release.gpg > > I: Checking Release signature > > I: Valid Release signature (key id > > 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500) > > I: Retrieving Packages > > I: Validating Packages > > I: Retrieving Packages > > I: Validating Packages > > I: Retrieving Packages > > I: Validating Packages > > I: Resolving dependencies of required packages... > > I: Resolving dependencies of base packages... > > I: Found additional required dependencies: libaudit1 libaudit- > > common libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 > > libgpg-error0 liblz4-1 libncursesw5 libsemanage1 libsemanage-common > > libsystemd0 libudev1 libustr-1.0-1 > > I: Found additional base dependencies: adduser debian-archive- > > keyring gpgv libapt-pkg5.0 libc-l10n libstdc++6 > > I: Checking component main on http://ftp.de.debian.org/debian. > > .. > > I: Retrieving libacl1 2.2.52-3+b1 > > I: Validating libacl1 2.2.52-3+b1 > > I: Retrieving adduser 3.115 > > I: Validating adduser 3.115 > > I: Retrieving apt 1.4.9 > > I: Validating apt 1.4.9 > > I: Retrieving libapt-pkg5.0 1.4.9 > > I: Validating libapt-pkg5.0 1.4.9 > > I: Retrieving libattr1 1:2.4.47-2+b2 > > I: Validating libattr1 1:2.4.47-2+b2 > > I: Retrieving libaudit-common 1:2.6.7-2 > > I: Validating libaudit-common 1:2.6.7-2 > > I: Retrieving libaudit1 1:2.6.7-2 > > I: Validating libaudit1 1:2.6.7-2 > > I: Retrieving base-files 9.9+deb9u8 > > I: Validating base-files 9.9+deb9u8 > > I: Retrieving base-passwd 3.5.43 > > I: Validating base-passwd 3.5.43 > > I: Retrieving bash 4.4-5 > > I: Validating bash 4.4-5 > > I: Retrieving libbz2-1.0 1.0.6-8.1 > > I: Validating libbz2-1.0 1.0.6-8.1 > > I: Retrieving libdebconfclient0 0.227 > > I: Validating libdebconfclient0 0.227 > > I: Retrieving coreutils 8.26-3 > > I: Validating coreutils 8.26-3 > > I: Retrieving dash 0.5.8-2.4 > > I: Validating dash 0.5.8-2.4 > > I: Retrieving libdb5.3 5.3.28-12+deb9u1 > > I: Validating libdb5.3 5.3.28-12+deb9u1 > > I: Retrieving debconf 1.5.61 > > I: Validating debconf 1.5.61 > > I: Retrieving debian-archive-keyring 2017.5 > > I: Validating debian-archive-keyring 2017.5 > > I: Retrieving debianutils 4.8.1.1 > > I: Validating debianutils 4.8.1.1 > > I: Retrieving diffutils 1:3.5-3 > > I: Validating diffutils 1:3.5-3 > > I: Retrieving dpkg 1.18.25 > > I: Validating dpkg 1.18.25 > > I: Retrieving e2fslibs 1.43.4-2 > > I: Validating e2fslibs 1.43.4-2 > > I: Retrieving e2fsprogs 1.43.4-2 > > I: Validating e2fsprogs 1.43.4-2 > > I: Retrieving libcomerr2 1.43.4-2 > > I: Validating libcomerr2 1.43.4-2 > > I: Retrieving libss2 1.43.4-2 > > I: Validating libss2 1.43.4-2 > > I: Retrieving findutils 4.6.0+git+20161106-2 > > I: Validating findutils 4.6.0+git+20161106-2 > > I: Retrieving gcc-6-base 6.3.0-18+deb9u1 > > I: Validating gcc-6-base 6.3.0-18+deb9u1 > > I: Retrieving libgcc1 1:6.3.0-18+deb9u1 > > I: Validating libgcc1 1:6.3.0-18+deb9u1 > > I: Retrieving libstdc++6 6.3.0-18+deb9u1 > > I: Validating libstdc++6 6.3.0-18+deb9u1 > > I: Retrieving libc-bin 2.24-11+deb9u4 > > I: Validating libc-bin 2.24-11+deb9u4 > > I: Retrieving libc-l10n 2.24-11+deb9u4 > > I: Validating libc-l10n 2.24-11+deb9u4 > > I: Retrieving libc6 2.24-11+deb9u4 > > I: Validating libc6 2.24-11+deb9u4 > > I: Retrieving locales 2.24-11+deb9u4 > > I: Validating locales 2.24-11+deb9u4 > > I: Retrieving multiarch-support 2.24-11+deb9u4 > > I: Validating multiarch-support 2.24-11+deb9u4 > > I: Retrieving gpgv 2.1.18-8~deb9u4 > > I: Validating gpgv 2.1.18-8~deb9u4 > > I: Retrieving grep 2.27-2 > > I: Validating grep 2.27-2 > > I: Retrieving gzip 1.6-5+b1 > > I: Validating gzip 1.6-5+b1 > > I: Retrieving hostname 3.18+b1 > > I: Validating hostname 3.18+b1 > > I: Retrieving init-system-helpers 1.48 > > I: Validating init-system-helpers 1.48 > > I: Retrieving libcap-ng0 0.7.7-3+b1 > > I: Validating libcap-ng0 0.7.7-3+b1 > > I: Retrieving libgcrypt20 1.7.6-2+deb9u3 > > I: Validating libgcrypt20 1.7.6-2+deb9u3 > > I: Retrieving libgpg-error0 1.26-2 > > I: Validating libgpg-error0 1.26-2 > > I: Retrieving libselinux1 2.6-3+b3 > > I: Validating libselinux1 2.6-3+b3 > > I: Retrieving libsemanage-common 2.6-2 > > I: Validating libsemanage-common 2.6-2 > > I: Retrieving libsemanage1 2.6-2 > > I: Validating libsemanage1 2.6-2 > > I: Retrieving libsepol1 2.6-2 > > I: Validating libsepol1 2.6-2 > > I: Retrieving lsb-base 9.20161125 > > I: Validating lsb-base 9.20161125 > > I: Retrieving liblz4-1 0.0~r131-2+b1 > > I: Validating liblz4-1 0.0~r131-2+b1 > > I: Retrieving mawk 1.3.3-17+b3 > > I: Validating mawk 1.3.3-17+b3 > > I: Retrieving libncursesw5 6.0+20161126-1+deb9u2 > > I: Validating libncursesw5 6.0+20161126-1+deb9u2 > > I: Retrieving libtinfo5 6.0+20161126-1+deb9u2 > > I: Validating libtinfo5 6.0+20161126-1+deb9u2 > > I: Retrieving ncurses-base 6.0+20161126-1+deb9u2 > > I: Validating ncurses-base 6.0+20161126-1+deb9u2 > > I: Retrieving ncurses-bin 6.0+20161126-1+deb9u2 > > I: Validating ncurses-bin 6.0+20161126-1+deb9u2 > > I: Retrieving libpam-modules 1.1.8-3.6 > > I: Validating libpam-modules 1.1.8-3.6 > > I: Retrieving libpam-modules-bin 1.1.8-3.6 > > I: Validating libpam-modules-bin 1.1.8-3.6 > > I: Retrieving libpam-runtime 1.1.8-3.6 > > I: Validating libpam-runtime 1.1.8-3.6 > > I: Retrieving libpam0g 1.1.8-3.6 > > I: Validating libpam0g 1.1.8-3.6 > > I: Retrieving libpcre3 2:8.39-3 > > I: Validating libpcre3 2:8.39-3 > > I: Retrieving perl-base 5.24.1-3+deb9u5 > > I: Validating perl-base 5.24.1-3+deb9u5 > > I: Retrieving sed 4.4-1 > > I: Validating sed 4.4-1 > > I: Retrieving sensible-utils 0.0.9+deb9u1 > > I: Validating sensible-utils 0.0.9+deb9u1 > > I: Retrieving login 1:4.4-4.1 > > I: Validating login 1:4.4-4.1 > > I: Retrieving passwd 1:4.4-4.1 > > I: Validating passwd 1:4.4-4.1 > > I: Retrieving libsystemd0 232-25+deb9u8 > > I: Validating libsystemd0 232-25+deb9u8 > > I: Retrieving libudev1 232-25+deb9u8 > > I: Validating libudev1 232-25+deb9u8 > > I: Retrieving sysvinit-utils 2.88dsf-59.9 > > I: Validating sysvinit-utils 2.88dsf-59.9 > > I: Retrieving tar 1.29b-1.1 > > I: Validating tar 1.29b-1.1 > > I: Retrieving tzdata 2018i-0+deb9u1 > > I: Validating tzdata 2018i-0+deb9u1 > > I: Retrieving libustr-1.0-1 1.0.4-6 > > I: Validating libustr-1.0-1 1.0.4-6 > > I: Retrieving bsdutils 1:2.29.2-1+deb9u1 > > I: Validating bsdutils 1:2.29.2-1+deb9u1 > > I: Retrieving libblkid1 2.29.2-1+deb9u1 > > I: Validating libblkid1 2.29.2-1+deb9u1 > > I: Retrieving libfdisk1 2.29.2-1+deb9u1 > > I: Validating libfdisk1 2.29.2-1+deb9u1 > > I: Retrieving libmount1 2.29.2-1+deb9u1 > > I: Validating libmount1 2.29.2-1+deb9u1 > > I: Retrieving libsmartcols1 2.29.2-1+deb9u1 > > I: Validating libsmartcols1 2.29.2-1+deb9u1 > > I: Retrieving libuuid1 2.29.2-1+deb9u1 > > I: Validating libuuid1 2.29.2-1+deb9u1 > > I: Retrieving mount 2.29.2-1+deb9u1 > > I: Validating mount 2.29.2-1+deb9u1 > > I: Retrieving util-linux 2.29.2-1+deb9u1 > > I: Validating util-linux 2.29.2-1+deb9u1 > > I: Retrieving liblzma5 5.2.2-1.2+b1 > > I: Validating liblzma5 5.2.2-1.2+b1 > > I: Retrieving zlib1g 1:1.2.8.dfsg-5 > > I: Validating zlib1g 1:1.2.8.dfsg-5 > > I: Chosen extractor for .deb packages: dpkg-deb > > I: Extracting libacl1... > > I: Extracting libattr1... > > I: Extracting libaudit-common... > > I: Extracting libaudit1... > > I: Extracting base-files... > > I: Extracting base-passwd... > > I: Extracting bash... > > I: Extracting libbz2-1.0... > > I: Extracting libdebconfclient0... > > I: Extracting coreutils... > > I: Extracting dash... > > I: Extracting libdb5.3... > > I: Extracting debconf... > > I: Extracting debianutils... > > I: Extracting diffutils... > > I: Extracting dpkg... > > I: Extracting e2fslibs... > > I: Extracting e2fsprogs... > > I: Extracting libcomerr2... > > I: Extracting libss2... > > I: Extracting findutils... > > I: Extracting gcc-6-base... > > I: Extracting libgcc1... > > I: Extracting libc-bin... > > I: Extracting libc6... > > I: Extracting multiarch-support... > > I: Extracting grep... > > I: Extracting gzip... > > I: Extracting hostname... > > I: Extracting init-system-helpers... > > I: Extracting libcap-ng0... > > I: Extracting libgcrypt20... > > I: Extracting libgpg-error0... > > I: Extracting libselinux1... > > I: Extracting libsemanage-common... > > I: Extracting libsemanage1... > > I: Extracting libsepol1... > > I: Extracting lsb-base... > > I: Extracting liblz4-1... > > I: Extracting mawk... > > I: Extracting libncursesw5... > > I: Extracting libtinfo5... > > I: Extracting ncurses-base... > > I: Extracting ncurses-bin... > > I: Extracting libpam-modules... > > I: Extracting libpam-modules-bin... > > I: Extracting libpam-runtime... > > I: Extracting libpam0g... > > I: Extracting libpcre3... > > I: Extracting perl-base... > > I: Extracting sed... > > I: Extracting sensible-utils... > > I: Extracting login... > > I: Extracting passwd... > > I: Extracting libsystemd0... > > I: Extracting libudev1... > > I: Extracting sysvinit-utils... > > I: Extracting tar... > > I: Extracting tzdata... > > I: Extracting libustr-1.0-1... > > I: Extracting bsdutils... > > I: Extracting libblkid1... > > I: Extracting libfdisk1... > > I: Extracting libmount1... > > I: Extracting libsmartcols1... > > I: Extracting libuuid1... > > I: Extracting mount... > > I: Extracting util-linux... > > I: Extracting liblzma5... > > I: Extracting zlib1g... > > I: Running command: chroot /work/build/tmp/work/cip-core- > > armhf/isar-bootstrap-target/rootfs /debootstrap/debootstrap -- > > second-stage > > chroot: failed to run command ‘/debootstrap/debootstrap’: No > > such file or directory > > WARNING: exit code 127 from a shell command. > > ERROR: Function failed: do_bootstrap (log file is located at > > /work/build/tmp/work/cip-core-armhf/isar-bootstrap- > > target/temp/log.do_bootstrap.316) > > > > Looping in isar-users and Claudius. I've no idea why debootstrap > should stumble here, apparently over its own feet. Well I would assume that it is an issue with your binfmt configuration if '/work/build/tmp/work/cip-core-armhf/isar-bootstrap- target/rootfs/debootstrap/deboostrap' exists. regards, Claudius > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux > ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-18 9:11 ` Claudius Heine @ 2019-03-18 9:39 ` Jan Kiszka 2019-03-18 10:14 ` akihiro27.suzuki 0 siblings, 1 reply; 15+ messages in thread From: Jan Kiszka @ 2019-03-18 9:39 UTC (permalink / raw) To: Claudius Heine, akihiro27.suzuki, isar-users, Claudius Heine Cc: daniel.sangorrin, cip-dev On 18.03.19 10:11, Claudius Heine wrote: > Hi, > > On Mon, 2019-03-18 at 10:05 +0100, [ext] Jan Kiszka wrote: >> On 18.03.19 02:42, akihiro27.suzuki@toshiba.co.jp wrote: >>> Hi Jan, >>> >>>> Were you building natively on Debian or inside the kas container? >>> I was executing following commands according to the README.md at >>> isar-cip-core, >>> so I think I was building inside the kas container. >>> >>> $ wget >>> https://raw.githubusercontent.com/siemens/kas/master/kas-docker >>> $ chmod a+x kas-docker >>> $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml >>> >>> The error is as follows (from log.do_bootstrap of isar-bootstrap- >>> target): >>> >>> DEBUG: Executing shell function do_bootstrap >>> I: Running command: debootstrap --arch armhf --foreign -- >>> verbose --variant=minbase --include=locales -- >>> components=main,contrib,non-free stretch /work/build/tmp/work/cip- >>> core-armhf/isar-bootstrap-target/rootfs >>> http://ftp.de.debian.org/debian >>> I: Retrieving InRelease >>> I: Retrieving Release >>> I: Retrieving Release.gpg >>> I: Checking Release signature >>> I: Valid Release signature (key id >>> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500) >>> I: Retrieving Packages >>> I: Validating Packages >>> I: Retrieving Packages >>> I: Validating Packages >>> I: Retrieving Packages >>> I: Validating Packages >>> I: Resolving dependencies of required packages... >>> I: Resolving dependencies of base packages... >>> I: Found additional required dependencies: libaudit1 libaudit- >>> common libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 >>> libgpg-error0 liblz4-1 libncursesw5 libsemanage1 libsemanage-common >>> libsystemd0 libudev1 libustr-1.0-1 >>> I: Found additional base dependencies: adduser debian-archive- >>> keyring gpgv libapt-pkg5.0 libc-l10n libstdc++6 >>> I: Checking component main on http://ftp.de.debian.org/debian. >>> .. >>> I: Retrieving libacl1 2.2.52-3+b1 >>> I: Validating libacl1 2.2.52-3+b1 >>> I: Retrieving adduser 3.115 >>> I: Validating adduser 3.115 >>> I: Retrieving apt 1.4.9 >>> I: Validating apt 1.4.9 >>> I: Retrieving libapt-pkg5.0 1.4.9 >>> I: Validating libapt-pkg5.0 1.4.9 >>> I: Retrieving libattr1 1:2.4.47-2+b2 >>> I: Validating libattr1 1:2.4.47-2+b2 >>> I: Retrieving libaudit-common 1:2.6.7-2 >>> I: Validating libaudit-common 1:2.6.7-2 >>> I: Retrieving libaudit1 1:2.6.7-2 >>> I: Validating libaudit1 1:2.6.7-2 >>> I: Retrieving base-files 9.9+deb9u8 >>> I: Validating base-files 9.9+deb9u8 >>> I: Retrieving base-passwd 3.5.43 >>> I: Validating base-passwd 3.5.43 >>> I: Retrieving bash 4.4-5 >>> I: Validating bash 4.4-5 >>> I: Retrieving libbz2-1.0 1.0.6-8.1 >>> I: Validating libbz2-1.0 1.0.6-8.1 >>> I: Retrieving libdebconfclient0 0.227 >>> I: Validating libdebconfclient0 0.227 >>> I: Retrieving coreutils 8.26-3 >>> I: Validating coreutils 8.26-3 >>> I: Retrieving dash 0.5.8-2.4 >>> I: Validating dash 0.5.8-2.4 >>> I: Retrieving libdb5.3 5.3.28-12+deb9u1 >>> I: Validating libdb5.3 5.3.28-12+deb9u1 >>> I: Retrieving debconf 1.5.61 >>> I: Validating debconf 1.5.61 >>> I: Retrieving debian-archive-keyring 2017.5 >>> I: Validating debian-archive-keyring 2017.5 >>> I: Retrieving debianutils 4.8.1.1 >>> I: Validating debianutils 4.8.1.1 >>> I: Retrieving diffutils 1:3.5-3 >>> I: Validating diffutils 1:3.5-3 >>> I: Retrieving dpkg 1.18.25 >>> I: Validating dpkg 1.18.25 >>> I: Retrieving e2fslibs 1.43.4-2 >>> I: Validating e2fslibs 1.43.4-2 >>> I: Retrieving e2fsprogs 1.43.4-2 >>> I: Validating e2fsprogs 1.43.4-2 >>> I: Retrieving libcomerr2 1.43.4-2 >>> I: Validating libcomerr2 1.43.4-2 >>> I: Retrieving libss2 1.43.4-2 >>> I: Validating libss2 1.43.4-2 >>> I: Retrieving findutils 4.6.0+git+20161106-2 >>> I: Validating findutils 4.6.0+git+20161106-2 >>> I: Retrieving gcc-6-base 6.3.0-18+deb9u1 >>> I: Validating gcc-6-base 6.3.0-18+deb9u1 >>> I: Retrieving libgcc1 1:6.3.0-18+deb9u1 >>> I: Validating libgcc1 1:6.3.0-18+deb9u1 >>> I: Retrieving libstdc++6 6.3.0-18+deb9u1 >>> I: Validating libstdc++6 6.3.0-18+deb9u1 >>> I: Retrieving libc-bin 2.24-11+deb9u4 >>> I: Validating libc-bin 2.24-11+deb9u4 >>> I: Retrieving libc-l10n 2.24-11+deb9u4 >>> I: Validating libc-l10n 2.24-11+deb9u4 >>> I: Retrieving libc6 2.24-11+deb9u4 >>> I: Validating libc6 2.24-11+deb9u4 >>> I: Retrieving locales 2.24-11+deb9u4 >>> I: Validating locales 2.24-11+deb9u4 >>> I: Retrieving multiarch-support 2.24-11+deb9u4 >>> I: Validating multiarch-support 2.24-11+deb9u4 >>> I: Retrieving gpgv 2.1.18-8~deb9u4 >>> I: Validating gpgv 2.1.18-8~deb9u4 >>> I: Retrieving grep 2.27-2 >>> I: Validating grep 2.27-2 >>> I: Retrieving gzip 1.6-5+b1 >>> I: Validating gzip 1.6-5+b1 >>> I: Retrieving hostname 3.18+b1 >>> I: Validating hostname 3.18+b1 >>> I: Retrieving init-system-helpers 1.48 >>> I: Validating init-system-helpers 1.48 >>> I: Retrieving libcap-ng0 0.7.7-3+b1 >>> I: Validating libcap-ng0 0.7.7-3+b1 >>> I: Retrieving libgcrypt20 1.7.6-2+deb9u3 >>> I: Validating libgcrypt20 1.7.6-2+deb9u3 >>> I: Retrieving libgpg-error0 1.26-2 >>> I: Validating libgpg-error0 1.26-2 >>> I: Retrieving libselinux1 2.6-3+b3 >>> I: Validating libselinux1 2.6-3+b3 >>> I: Retrieving libsemanage-common 2.6-2 >>> I: Validating libsemanage-common 2.6-2 >>> I: Retrieving libsemanage1 2.6-2 >>> I: Validating libsemanage1 2.6-2 >>> I: Retrieving libsepol1 2.6-2 >>> I: Validating libsepol1 2.6-2 >>> I: Retrieving lsb-base 9.20161125 >>> I: Validating lsb-base 9.20161125 >>> I: Retrieving liblz4-1 0.0~r131-2+b1 >>> I: Validating liblz4-1 0.0~r131-2+b1 >>> I: Retrieving mawk 1.3.3-17+b3 >>> I: Validating mawk 1.3.3-17+b3 >>> I: Retrieving libncursesw5 6.0+20161126-1+deb9u2 >>> I: Validating libncursesw5 6.0+20161126-1+deb9u2 >>> I: Retrieving libtinfo5 6.0+20161126-1+deb9u2 >>> I: Validating libtinfo5 6.0+20161126-1+deb9u2 >>> I: Retrieving ncurses-base 6.0+20161126-1+deb9u2 >>> I: Validating ncurses-base 6.0+20161126-1+deb9u2 >>> I: Retrieving ncurses-bin 6.0+20161126-1+deb9u2 >>> I: Validating ncurses-bin 6.0+20161126-1+deb9u2 >>> I: Retrieving libpam-modules 1.1.8-3.6 >>> I: Validating libpam-modules 1.1.8-3.6 >>> I: Retrieving libpam-modules-bin 1.1.8-3.6 >>> I: Validating libpam-modules-bin 1.1.8-3.6 >>> I: Retrieving libpam-runtime 1.1.8-3.6 >>> I: Validating libpam-runtime 1.1.8-3.6 >>> I: Retrieving libpam0g 1.1.8-3.6 >>> I: Validating libpam0g 1.1.8-3.6 >>> I: Retrieving libpcre3 2:8.39-3 >>> I: Validating libpcre3 2:8.39-3 >>> I: Retrieving perl-base 5.24.1-3+deb9u5 >>> I: Validating perl-base 5.24.1-3+deb9u5 >>> I: Retrieving sed 4.4-1 >>> I: Validating sed 4.4-1 >>> I: Retrieving sensible-utils 0.0.9+deb9u1 >>> I: Validating sensible-utils 0.0.9+deb9u1 >>> I: Retrieving login 1:4.4-4.1 >>> I: Validating login 1:4.4-4.1 >>> I: Retrieving passwd 1:4.4-4.1 >>> I: Validating passwd 1:4.4-4.1 >>> I: Retrieving libsystemd0 232-25+deb9u8 >>> I: Validating libsystemd0 232-25+deb9u8 >>> I: Retrieving libudev1 232-25+deb9u8 >>> I: Validating libudev1 232-25+deb9u8 >>> I: Retrieving sysvinit-utils 2.88dsf-59.9 >>> I: Validating sysvinit-utils 2.88dsf-59.9 >>> I: Retrieving tar 1.29b-1.1 >>> I: Validating tar 1.29b-1.1 >>> I: Retrieving tzdata 2018i-0+deb9u1 >>> I: Validating tzdata 2018i-0+deb9u1 >>> I: Retrieving libustr-1.0-1 1.0.4-6 >>> I: Validating libustr-1.0-1 1.0.4-6 >>> I: Retrieving bsdutils 1:2.29.2-1+deb9u1 >>> I: Validating bsdutils 1:2.29.2-1+deb9u1 >>> I: Retrieving libblkid1 2.29.2-1+deb9u1 >>> I: Validating libblkid1 2.29.2-1+deb9u1 >>> I: Retrieving libfdisk1 2.29.2-1+deb9u1 >>> I: Validating libfdisk1 2.29.2-1+deb9u1 >>> I: Retrieving libmount1 2.29.2-1+deb9u1 >>> I: Validating libmount1 2.29.2-1+deb9u1 >>> I: Retrieving libsmartcols1 2.29.2-1+deb9u1 >>> I: Validating libsmartcols1 2.29.2-1+deb9u1 >>> I: Retrieving libuuid1 2.29.2-1+deb9u1 >>> I: Validating libuuid1 2.29.2-1+deb9u1 >>> I: Retrieving mount 2.29.2-1+deb9u1 >>> I: Validating mount 2.29.2-1+deb9u1 >>> I: Retrieving util-linux 2.29.2-1+deb9u1 >>> I: Validating util-linux 2.29.2-1+deb9u1 >>> I: Retrieving liblzma5 5.2.2-1.2+b1 >>> I: Validating liblzma5 5.2.2-1.2+b1 >>> I: Retrieving zlib1g 1:1.2.8.dfsg-5 >>> I: Validating zlib1g 1:1.2.8.dfsg-5 >>> I: Chosen extractor for .deb packages: dpkg-deb >>> I: Extracting libacl1... >>> I: Extracting libattr1... >>> I: Extracting libaudit-common... >>> I: Extracting libaudit1... >>> I: Extracting base-files... >>> I: Extracting base-passwd... >>> I: Extracting bash... >>> I: Extracting libbz2-1.0... >>> I: Extracting libdebconfclient0... >>> I: Extracting coreutils... >>> I: Extracting dash... >>> I: Extracting libdb5.3... >>> I: Extracting debconf... >>> I: Extracting debianutils... >>> I: Extracting diffutils... >>> I: Extracting dpkg... >>> I: Extracting e2fslibs... >>> I: Extracting e2fsprogs... >>> I: Extracting libcomerr2... >>> I: Extracting libss2... >>> I: Extracting findutils... >>> I: Extracting gcc-6-base... >>> I: Extracting libgcc1... >>> I: Extracting libc-bin... >>> I: Extracting libc6... >>> I: Extracting multiarch-support... >>> I: Extracting grep... >>> I: Extracting gzip... >>> I: Extracting hostname... >>> I: Extracting init-system-helpers... >>> I: Extracting libcap-ng0... >>> I: Extracting libgcrypt20... >>> I: Extracting libgpg-error0... >>> I: Extracting libselinux1... >>> I: Extracting libsemanage-common... >>> I: Extracting libsemanage1... >>> I: Extracting libsepol1... >>> I: Extracting lsb-base... >>> I: Extracting liblz4-1... >>> I: Extracting mawk... >>> I: Extracting libncursesw5... >>> I: Extracting libtinfo5... >>> I: Extracting ncurses-base... >>> I: Extracting ncurses-bin... >>> I: Extracting libpam-modules... >>> I: Extracting libpam-modules-bin... >>> I: Extracting libpam-runtime... >>> I: Extracting libpam0g... >>> I: Extracting libpcre3... >>> I: Extracting perl-base... >>> I: Extracting sed... >>> I: Extracting sensible-utils... >>> I: Extracting login... >>> I: Extracting passwd... >>> I: Extracting libsystemd0... >>> I: Extracting libudev1... >>> I: Extracting sysvinit-utils... >>> I: Extracting tar... >>> I: Extracting tzdata... >>> I: Extracting libustr-1.0-1... >>> I: Extracting bsdutils... >>> I: Extracting libblkid1... >>> I: Extracting libfdisk1... >>> I: Extracting libmount1... >>> I: Extracting libsmartcols1... >>> I: Extracting libuuid1... >>> I: Extracting mount... >>> I: Extracting util-linux... >>> I: Extracting liblzma5... >>> I: Extracting zlib1g... >>> I: Running command: chroot /work/build/tmp/work/cip-core- >>> armhf/isar-bootstrap-target/rootfs /debootstrap/debootstrap -- >>> second-stage >>> chroot: failed to run command ‘/debootstrap/debootstrap’: No >>> such file or directory >>> WARNING: exit code 127 from a shell command. >>> ERROR: Function failed: do_bootstrap (log file is located at >>> /work/build/tmp/work/cip-core-armhf/isar-bootstrap- >>> target/temp/log.do_bootstrap.316) >>> >> >> Looping in isar-users and Claudius. I've no idea why debootstrap >> should stumble here, apparently over its own feet. > > Well I would assume that it is an issue with your binfmt configuration > if '/work/build/tmp/work/cip-core-armhf/isar-bootstrap- > target/rootfs/debootstrap/deboostrap' exists. > 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. If that should have been the reason, we likely need a better detection in Isar, before the user runs into this non-obvious error message. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: debootrap error 2019-03-18 9:39 ` debootrap error Jan Kiszka @ 2019-03-18 10:14 ` akihiro27.suzuki 2019-03-18 10:17 ` Claudius Heine 0 siblings, 1 reply; 15+ messages in thread From: akihiro27.suzuki @ 2019-03-18 10:14 UTC (permalink / raw) To: jan.kiszka, claudius.heine.ext, isar-users, ch; +Cc: daniel.sangorrin, cip-dev 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 The startup message is as follows: $ ./kas-docker --isar build kas.yml:board-bbb.yml 2019-03-18 10:08:58 - INFO - kas 0.20.1 started 2019-03-18 10:08:58 - INFO - /repo$ git rev-parse --show-toplevel 2019-03-18 10:08:58 - INFO - /repo$ git rev-parse --show-toplevel 2019-03-18 10:08:58 - INFO - /repo$ git rev-parse --show-toplevel 2019-03-18 10:08:58 - INFO - Using /repo as root for repository cip-core 2019-03-18 10:08:58 - INFO - /work$ git clone -q https://github.com/ilbers/isar /work/isar 2019-03-18 10:09:02 - INFO - Repository isar cloned 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core 2019-03-18 10:09:02 - INFO - /work/isar$ git status -s 2019-03-18 10:09:02 - INFO - /work/isar$ git rev-parse --verify HEAD 2019-03-18 10:09:02 - INFO - 6c5db020b9b837d7b0ce63bfc719f9192e725f26 2019-03-18 10:09:02 - INFO - /work/isar$ git checkout -q d226c29d24f791a15fbdce9c354eb189a1003dcc 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core 2019-03-18 10:09:02 - INFO - /work/isar$ /tmp/tmpyscgo7lw /work/build 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core 2019-03-18 10:09:02 - INFO - /work/build$ /work/isar/bitbake/bin/bitbake -k -c build cip-core-image Parsing recipes: 100% |################################################################################ ...(snip)... Best regards, Suzuki > -----Original Message----- > From: Jan Kiszka [mailto:jan.kiszka@siemens.com] > Sent: Monday, March 18, 2019 6:39 PM > To: Claudius Heine <claudius.heine.ext@siemens.com>; suzuki akihiro(鈴 > 木 章浩 ○ＳＷＣ□ＯＳＴ) <akihiro27.suzuki@toshiba.co.jp>; > isar-users <isar-users@googlegroups.com>; Claudius Heine <ch@denx.de> > Cc: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) > <daniel.sangorrin@toshiba.co.jp>; cip-dev@lists.cip-project.org > Subject: Re: debootrap error > > On 18.03.19 10:11, Claudius Heine wrote: > > Hi, > > > > On Mon, 2019-03-18 at 10:05 +0100, [ext] Jan Kiszka wrote: > >> On 18.03.19 02:42, akihiro27.suzuki@toshiba.co.jp wrote: > >>> Hi Jan, > >>> > >>>> Were you building natively on Debian or inside the kas container? > >>> I was executing following commands according to the README.md at > >>> isar-cip-core, > >>> so I think I was building inside the kas container. > >>> > >>> $ wget > >>> https://raw.githubusercontent.com/siemens/kas/master/kas-docker > >>> $ chmod a+x kas-docker > >>> $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml > >>> > >>> The error is as follows (from log.do_bootstrap of isar-bootstrap- > >>> target): > >>> > >>> DEBUG: Executing shell function do_bootstrap > >>> I: Running command: debootstrap --arch armhf --foreign -- > >>> verbose --variant=minbase --include=locales -- > >>> components=main,contrib,non-free stretch /work/build/tmp/work/cip- > >>> core-armhf/isar-bootstrap-target/rootfs > >>> http://ftp.de.debian.org/debian > >>> I: Retrieving InRelease > >>> I: Retrieving Release > >>> I: Retrieving Release.gpg > >>> I: Checking Release signature > >>> I: Valid Release signature (key id > >>> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500) > >>> I: Retrieving Packages > >>> I: Validating Packages > >>> I: Retrieving Packages > >>> I: Validating Packages > >>> I: Retrieving Packages > >>> I: Validating Packages > >>> I: Resolving dependencies of required packages... > >>> I: Resolving dependencies of base packages... > >>> I: Found additional required dependencies: libaudit1 > libaudit- > >>> common libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 > >>> libgpg-error0 liblz4-1 libncursesw5 libsemanage1 libsemanage-common > >>> libsystemd0 libudev1 libustr-1.0-1 > >>> I: Found additional base dependencies: adduser > debian-archive- > >>> keyring gpgv libapt-pkg5.0 libc-l10n libstdc++6 > >>> I: Checking component main on > http://ftp.de.debian.org/debian. > >>> .. > >>> I: Retrieving libacl1 2.2.52-3+b1 > >>> I: Validating libacl1 2.2.52-3+b1 > >>> I: Retrieving adduser 3.115 > >>> I: Validating adduser 3.115 > >>> I: Retrieving apt 1.4.9 > >>> I: Validating apt 1.4.9 > >>> I: Retrieving libapt-pkg5.0 1.4.9 > >>> I: Validating libapt-pkg5.0 1.4.9 > >>> I: Retrieving libattr1 1:2.4.47-2+b2 > >>> I: Validating libattr1 1:2.4.47-2+b2 > >>> I: Retrieving libaudit-common 1:2.6.7-2 > >>> I: Validating libaudit-common 1:2.6.7-2 > >>> I: Retrieving libaudit1 1:2.6.7-2 > >>> I: Validating libaudit1 1:2.6.7-2 > >>> I: Retrieving base-files 9.9+deb9u8 > >>> I: Validating base-files 9.9+deb9u8 > >>> I: Retrieving base-passwd 3.5.43 > >>> I: Validating base-passwd 3.5.43 > >>> I: Retrieving bash 4.4-5 > >>> I: Validating bash 4.4-5 > >>> I: Retrieving libbz2-1.0 1.0.6-8.1 > >>> I: Validating libbz2-1.0 1.0.6-8.1 > >>> I: Retrieving libdebconfclient0 0.227 > >>> I: Validating libdebconfclient0 0.227 > >>> I: Retrieving coreutils 8.26-3 > >>> I: Validating coreutils 8.26-3 > >>> I: Retrieving dash 0.5.8-2.4 > >>> I: Validating dash 0.5.8-2.4 > >>> I: Retrieving libdb5.3 5.3.28-12+deb9u1 > >>> I: Validating libdb5.3 5.3.28-12+deb9u1 > >>> I: Retrieving debconf 1.5.61 > >>> I: Validating debconf 1.5.61 > >>> I: Retrieving debian-archive-keyring 2017.5 > >>> I: Validating debian-archive-keyring 2017.5 > >>> I: Retrieving debianutils 4.8.1.1 > >>> I: Validating debianutils 4.8.1.1 > >>> I: Retrieving diffutils 1:3.5-3 > >>> I: Validating diffutils 1:3.5-3 > >>> I: Retrieving dpkg 1.18.25 > >>> I: Validating dpkg 1.18.25 > >>> I: Retrieving e2fslibs 1.43.4-2 > >>> I: Validating e2fslibs 1.43.4-2 > >>> I: Retrieving e2fsprogs 1.43.4-2 > >>> I: Validating e2fsprogs 1.43.4-2 > >>> I: Retrieving libcomerr2 1.43.4-2 > >>> I: Validating libcomerr2 1.43.4-2 > >>> I: Retrieving libss2 1.43.4-2 > >>> I: Validating libss2 1.43.4-2 > >>> I: Retrieving findutils 4.6.0+git+20161106-2 > >>> I: Validating findutils 4.6.0+git+20161106-2 > >>> I: Retrieving gcc-6-base 6.3.0-18+deb9u1 > >>> I: Validating gcc-6-base 6.3.0-18+deb9u1 > >>> I: Retrieving libgcc1 1:6.3.0-18+deb9u1 > >>> I: Validating libgcc1 1:6.3.0-18+deb9u1 > >>> I: Retrieving libstdc++6 6.3.0-18+deb9u1 > >>> I: Validating libstdc++6 6.3.0-18+deb9u1 > >>> I: Retrieving libc-bin 2.24-11+deb9u4 > >>> I: Validating libc-bin 2.24-11+deb9u4 > >>> I: Retrieving libc-l10n 2.24-11+deb9u4 > >>> I: Validating libc-l10n 2.24-11+deb9u4 > >>> I: Retrieving libc6 2.24-11+deb9u4 > >>> I: Validating libc6 2.24-11+deb9u4 > >>> I: Retrieving locales 2.24-11+deb9u4 > >>> I: Validating locales 2.24-11+deb9u4 > >>> I: Retrieving multiarch-support 2.24-11+deb9u4 > >>> I: Validating multiarch-support 2.24-11+deb9u4 > >>> I: Retrieving gpgv 2.1.18-8~deb9u4 > >>> I: Validating gpgv 2.1.18-8~deb9u4 > >>> I: Retrieving grep 2.27-2 > >>> I: Validating grep 2.27-2 > >>> I: Retrieving gzip 1.6-5+b1 > >>> I: Validating gzip 1.6-5+b1 > >>> I: Retrieving hostname 3.18+b1 > >>> I: Validating hostname 3.18+b1 > >>> I: Retrieving init-system-helpers 1.48 > >>> I: Validating init-system-helpers 1.48 > >>> I: Retrieving libcap-ng0 0.7.7-3+b1 > >>> I: Validating libcap-ng0 0.7.7-3+b1 > >>> I: Retrieving libgcrypt20 1.7.6-2+deb9u3 > >>> I: Validating libgcrypt20 1.7.6-2+deb9u3 > >>> I: Retrieving libgpg-error0 1.26-2 > >>> I: Validating libgpg-error0 1.26-2 > >>> I: Retrieving libselinux1 2.6-3+b3 > >>> I: Validating libselinux1 2.6-3+b3 > >>> I: Retrieving libsemanage-common 2.6-2 > >>> I: Validating libsemanage-common 2.6-2 > >>> I: Retrieving libsemanage1 2.6-2 > >>> I: Validating libsemanage1 2.6-2 > >>> I: Retrieving libsepol1 2.6-2 > >>> I: Validating libsepol1 2.6-2 > >>> I: Retrieving lsb-base 9.20161125 > >>> I: Validating lsb-base 9.20161125 > >>> I: Retrieving liblz4-1 0.0~r131-2+b1 > >>> I: Validating liblz4-1 0.0~r131-2+b1 > >>> I: Retrieving mawk 1.3.3-17+b3 > >>> I: Validating mawk 1.3.3-17+b3 > >>> I: Retrieving libncursesw5 6.0+20161126-1+deb9u2 > >>> I: Validating libncursesw5 6.0+20161126-1+deb9u2 > >>> I: Retrieving libtinfo5 6.0+20161126-1+deb9u2 > >>> I: Validating libtinfo5 6.0+20161126-1+deb9u2 > >>> I: Retrieving ncurses-base 6.0+20161126-1+deb9u2 > >>> I: Validating ncurses-base 6.0+20161126-1+deb9u2 > >>> I: Retrieving ncurses-bin 6.0+20161126-1+deb9u2 > >>> I: Validating ncurses-bin 6.0+20161126-1+deb9u2 > >>> I: Retrieving libpam-modules 1.1.8-3.6 > >>> I: Validating libpam-modules 1.1.8-3.6 > >>> I: Retrieving libpam-modules-bin 1.1.8-3.6 > >>> I: Validating libpam-modules-bin 1.1.8-3.6 > >>> I: Retrieving libpam-runtime 1.1.8-3.6 > >>> I: Validating libpam-runtime 1.1.8-3.6 > >>> I: Retrieving libpam0g 1.1.8-3.6 > >>> I: Validating libpam0g 1.1.8-3.6 > >>> I: Retrieving libpcre3 2:8.39-3 > >>> I: Validating libpcre3 2:8.39-3 > >>> I: Retrieving perl-base 5.24.1-3+deb9u5 > >>> I: Validating perl-base 5.24.1-3+deb9u5 > >>> I: Retrieving sed 4.4-1 > >>> I: Validating sed 4.4-1 > >>> I: Retrieving sensible-utils 0.0.9+deb9u1 > >>> I: Validating sensible-utils 0.0.9+deb9u1 > >>> I: Retrieving login 1:4.4-4.1 > >>> I: Validating login 1:4.4-4.1 > >>> I: Retrieving passwd 1:4.4-4.1 > >>> I: Validating passwd 1:4.4-4.1 > >>> I: Retrieving libsystemd0 232-25+deb9u8 > >>> I: Validating libsystemd0 232-25+deb9u8 > >>> I: Retrieving libudev1 232-25+deb9u8 > >>> I: Validating libudev1 232-25+deb9u8 > >>> I: Retrieving sysvinit-utils 2.88dsf-59.9 > >>> I: Validating sysvinit-utils 2.88dsf-59.9 > >>> I: Retrieving tar 1.29b-1.1 > >>> I: Validating tar 1.29b-1.1 > >>> I: Retrieving tzdata 2018i-0+deb9u1 > >>> I: Validating tzdata 2018i-0+deb9u1 > >>> I: Retrieving libustr-1.0-1 1.0.4-6 > >>> I: Validating libustr-1.0-1 1.0.4-6 > >>> I: Retrieving bsdutils 1:2.29.2-1+deb9u1 > >>> I: Validating bsdutils 1:2.29.2-1+deb9u1 > >>> I: Retrieving libblkid1 2.29.2-1+deb9u1 > >>> I: Validating libblkid1 2.29.2-1+deb9u1 > >>> I: Retrieving libfdisk1 2.29.2-1+deb9u1 > >>> I: Validating libfdisk1 2.29.2-1+deb9u1 > >>> I: Retrieving libmount1 2.29.2-1+deb9u1 > >>> I: Validating libmount1 2.29.2-1+deb9u1 > >>> I: Retrieving libsmartcols1 2.29.2-1+deb9u1 > >>> I: Validating libsmartcols1 2.29.2-1+deb9u1 > >>> I: Retrieving libuuid1 2.29.2-1+deb9u1 > >>> I: Validating libuuid1 2.29.2-1+deb9u1 > >>> I: Retrieving mount 2.29.2-1+deb9u1 > >>> I: Validating mount 2.29.2-1+deb9u1 > >>> I: Retrieving util-linux 2.29.2-1+deb9u1 > >>> I: Validating util-linux 2.29.2-1+deb9u1 > >>> I: Retrieving liblzma5 5.2.2-1.2+b1 > >>> I: Validating liblzma5 5.2.2-1.2+b1 > >>> I: Retrieving zlib1g 1:1.2.8.dfsg-5 > >>> I: Validating zlib1g 1:1.2.8.dfsg-5 > >>> I: Chosen extractor for .deb packages: dpkg-deb > >>> I: Extracting libacl1... > >>> I: Extracting libattr1... > >>> I: Extracting libaudit-common... > >>> I: Extracting libaudit1... > >>> I: Extracting base-files... > >>> I: Extracting base-passwd... > >>> I: Extracting bash... > >>> I: Extracting libbz2-1.0... > >>> I: Extracting libdebconfclient0... > >>> I: Extracting coreutils... > >>> I: Extracting dash... > >>> I: Extracting libdb5.3... > >>> I: Extracting debconf... > >>> I: Extracting debianutils... > >>> I: Extracting diffutils... > >>> I: Extracting dpkg... > >>> I: Extracting e2fslibs... > >>> I: Extracting e2fsprogs... > >>> I: Extracting libcomerr2... > >>> I: Extracting libss2... > >>> I: Extracting findutils... > >>> I: Extracting gcc-6-base... > >>> I: Extracting libgcc1... > >>> I: Extracting libc-bin... > >>> I: Extracting libc6... > >>> I: Extracting multiarch-support... > >>> I: Extracting grep... > >>> I: Extracting gzip... > >>> I: Extracting hostname... > >>> I: Extracting init-system-helpers... > >>> I: Extracting libcap-ng0... > >>> I: Extracting libgcrypt20... > >>> I: Extracting libgpg-error0... > >>> I: Extracting libselinux1... > >>> I: Extracting libsemanage-common... > >>> I: Extracting libsemanage1... > >>> I: Extracting libsepol1... > >>> I: Extracting lsb-base... > >>> I: Extracting liblz4-1... > >>> I: Extracting mawk... > >>> I: Extracting libncursesw5... > >>> I: Extracting libtinfo5... > >>> I: Extracting ncurses-base... > >>> I: Extracting ncurses-bin... > >>> I: Extracting libpam-modules... > >>> I: Extracting libpam-modules-bin... > >>> I: Extracting libpam-runtime... > >>> I: Extracting libpam0g... > >>> I: Extracting libpcre3... > >>> I: Extracting perl-base... > >>> I: Extracting sed... > >>> I: Extracting sensible-utils... > >>> I: Extracting login... > >>> I: Extracting passwd... > >>> I: Extracting libsystemd0... > >>> I: Extracting libudev1... > >>> I: Extracting sysvinit-utils... > >>> I: Extracting tar... > >>> I: Extracting tzdata... > >>> I: Extracting libustr-1.0-1... > >>> I: Extracting bsdutils... > >>> I: Extracting libblkid1... > >>> I: Extracting libfdisk1... > >>> I: Extracting libmount1... > >>> I: Extracting libsmartcols1... > >>> I: Extracting libuuid1... > >>> I: Extracting mount... > >>> I: Extracting util-linux... > >>> I: Extracting liblzma5... > >>> I: Extracting zlib1g... > >>> I: Running command: chroot /work/build/tmp/work/cip-core- > >>> armhf/isar-bootstrap-target/rootfs /debootstrap/debootstrap -- > >>> second-stage > >>> chroot: failed to run command ‘/debootstrap/debootstrap’: No > >>> such file or directory > >>> WARNING: exit code 127 from a shell command. > >>> ERROR: Function failed: do_bootstrap (log file is located at > >>> /work/build/tmp/work/cip-core-armhf/isar-bootstrap- > >>> target/temp/log.do_bootstrap.316) > >>> > >> > >> Looping in isar-users and Claudius. I've no idea why debootstrap > >> should stumble here, apparently over its own feet. > > > > Well I would assume that it is an issue with your binfmt configuration > > if '/work/build/tmp/work/cip-core-armhf/isar-bootstrap- > > target/rootfs/debootstrap/deboostrap' exists. > > > > 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. > > If that should have been the reason, we likely need a better detection > in Isar, > before the user runs into this non-obvious error message. > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-18 10:14 ` akihiro27.suzuki @ 2019-03-18 10:17 ` Claudius Heine 2019-03-18 10:18 ` Jan Kiszka 0 siblings, 1 reply; 15+ messages in thread From: Claudius Heine @ 2019-03-18 10:17 UTC (permalink / raw) To: akihiro27.suzuki, jan.kiszka, isar-users, ch; +Cc: daniel.sangorrin, cip-dev 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? $ cat /proc/sys/fs/binfmt_misc/qemu-arm enabled interpreter /usr/bin/qemu-arm-static flags: OCF offset 0 magic 7f454c4601010100000000000000000002002800 mask ffffffffffffff00fffffffffffffffffeffffff regards, Claudius > > The startup message is as follows: > > $ ./kas-docker --isar build kas.yml:board-bbb.yml > 2019-03-18 10:08:58 - INFO - kas 0.20.1 started > 2019-03-18 10:08:58 - INFO - /repo$ git rev-parse --show-toplevel > 2019-03-18 10:08:58 - INFO - /repo$ git rev-parse --show-toplevel > 2019-03-18 10:08:58 - INFO - /repo$ git rev-parse --show-toplevel > 2019-03-18 10:08:58 - INFO - Using /repo as root for repository cip-core > 2019-03-18 10:08:58 - INFO - /work$ git clone -q https://github.com/ilbers/isar /work/isar > 2019-03-18 10:09:02 - INFO - Repository isar cloned > 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel > 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core > 2019-03-18 10:09:02 - INFO - /work/isar$ git status -s > 2019-03-18 10:09:02 - INFO - /work/isar$ git rev-parse --verify HEAD > 2019-03-18 10:09:02 - INFO - 6c5db020b9b837d7b0ce63bfc719f9192e725f26 > 2019-03-18 10:09:02 - INFO - /work/isar$ git checkout -q d226c29d24f791a15fbdce9c354eb189a1003dcc > 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel > 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core > 2019-03-18 10:09:02 - INFO - /work/isar$ /tmp/tmpyscgo7lw /work/build > 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel > 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core > 2019-03-18 10:09:02 - INFO - /repo$ git rev-parse --show-toplevel > 2019-03-18 10:09:02 - INFO - Using /repo as root for repository cip-core > 2019-03-18 10:09:02 - INFO - /work/build$ /work/isar/bitbake/bin/bitbake -k -c build cip-core-image > Parsing recipes: 100% |################################################################################ > ...(snip)... > > Best regards, > Suzuki > > >> -----Original Message----- >> From: Jan Kiszka [mailto:jan.kiszka@siemens.com] >> Sent: Monday, March 18, 2019 6:39 PM >> To: Claudius Heine <claudius.heine.ext@siemens.com>; suzuki akihiro(鈴 >> 木 章浩 ○ＳＷＣ□ＯＳＴ) <akihiro27.suzuki@toshiba.co.jp>; >> isar-users <isar-users@googlegroups.com>; Claudius Heine <ch@denx.de> >> Cc: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) >> <daniel.sangorrin@toshiba.co.jp>; cip-dev@lists.cip-project.org >> Subject: Re: debootrap error >> >> On 18.03.19 10:11, Claudius Heine wrote: >>> Hi, >>> >>> On Mon, 2019-03-18 at 10:05 +0100, [ext] Jan Kiszka wrote: >>>> On 18.03.19 02:42, akihiro27.suzuki@toshiba.co.jp wrote: >>>>> Hi Jan, >>>>> >>>>>> Were you building natively on Debian or inside the kas container? >>>>> I was executing following commands according to the README.md at >>>>> isar-cip-core, >>>>> so I think I was building inside the kas container. >>>>> >>>>> $ wget >>>>> https://raw.githubusercontent.com/siemens/kas/master/kas-docker >>>>> $ chmod a+x kas-docker >>>>> $ sudo ./kas-docker --isar build kas.yml:board-bbb.yml >>>>> >>>>> The error is as follows (from log.do_bootstrap of isar-bootstrap- >>>>> target): >>>>> >>>>> DEBUG: Executing shell function do_bootstrap >>>>> I: Running command: debootstrap --arch armhf --foreign -- >>>>> verbose --variant=minbase --include=locales -- >>>>> components=main,contrib,non-free stretch /work/build/tmp/work/cip- >>>>> core-armhf/isar-bootstrap-target/rootfs >>>>> http://ftp.de.debian.org/debian >>>>> I: Retrieving InRelease >>>>> I: Retrieving Release >>>>> I: Retrieving Release.gpg >>>>> I: Checking Release signature >>>>> I: Valid Release signature (key id >>>>> 067E3C456BAE240ACEE88F6FEF0F382A1A7B6500) >>>>> I: Retrieving Packages >>>>> I: Validating Packages >>>>> I: Retrieving Packages >>>>> I: Validating Packages >>>>> I: Retrieving Packages >>>>> I: Validating Packages >>>>> I: Resolving dependencies of required packages... >>>>> I: Resolving dependencies of base packages... >>>>> I: Found additional required dependencies: libaudit1 >> libaudit- >>>>> common libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 >>>>> libgpg-error0 liblz4-1 libncursesw5 libsemanage1 libsemanage-common >>>>> libsystemd0 libudev1 libustr-1.0-1 >>>>> I: Found additional base dependencies: adduser >> debian-archive- >>>>> keyring gpgv libapt-pkg5.0 libc-l10n libstdc++6 >>>>> I: Checking component main on >> http://ftp.de.debian.org/debian. >>>>> .. >>>>> I: Retrieving libacl1 2.2.52-3+b1 >>>>> I: Validating libacl1 2.2.52-3+b1 >>>>> I: Retrieving adduser 3.115 >>>>> I: Validating adduser 3.115 >>>>> I: Retrieving apt 1.4.9 >>>>> I: Validating apt 1.4.9 >>>>> I: Retrieving libapt-pkg5.0 1.4.9 >>>>> I: Validating libapt-pkg5.0 1.4.9 >>>>> I: Retrieving libattr1 1:2.4.47-2+b2 >>>>> I: Validating libattr1 1:2.4.47-2+b2 >>>>> I: Retrieving libaudit-common 1:2.6.7-2 >>>>> I: Validating libaudit-common 1:2.6.7-2 >>>>> I: Retrieving libaudit1 1:2.6.7-2 >>>>> I: Validating libaudit1 1:2.6.7-2 >>>>> I: Retrieving base-files 9.9+deb9u8 >>>>> I: Validating base-files 9.9+deb9u8 >>>>> I: Retrieving base-passwd 3.5.43 >>>>> I: Validating base-passwd 3.5.43 >>>>> I: Retrieving bash 4.4-5 >>>>> I: Validating bash 4.4-5 >>>>> I: Retrieving libbz2-1.0 1.0.6-8.1 >>>>> I: Validating libbz2-1.0 1.0.6-8.1 >>>>> I: Retrieving libdebconfclient0 0.227 >>>>> I: Validating libdebconfclient0 0.227 >>>>> I: Retrieving coreutils 8.26-3 >>>>> I: Validating coreutils 8.26-3 >>>>> I: Retrieving dash 0.5.8-2.4 >>>>> I: Validating dash 0.5.8-2.4 >>>>> I: Retrieving libdb5.3 5.3.28-12+deb9u1 >>>>> I: Validating libdb5.3 5.3.28-12+deb9u1 >>>>> I: Retrieving debconf 1.5.61 >>>>> I: Validating debconf 1.5.61 >>>>> I: Retrieving debian-archive-keyring 2017.5 >>>>> I: Validating debian-archive-keyring 2017.5 >>>>> I: Retrieving debianutils 4.8.1.1 >>>>> I: Validating debianutils 4.8.1.1 >>>>> I: Retrieving diffutils 1:3.5-3 >>>>> I: Validating diffutils 1:3.5-3 >>>>> I: Retrieving dpkg 1.18.25 >>>>> I: Validating dpkg 1.18.25 >>>>> I: Retrieving e2fslibs 1.43.4-2 >>>>> I: Validating e2fslibs 1.43.4-2 >>>>> I: Retrieving e2fsprogs 1.43.4-2 >>>>> I: Validating e2fsprogs 1.43.4-2 >>>>> I: Retrieving libcomerr2 1.43.4-2 >>>>> I: Validating libcomerr2 1.43.4-2 >>>>> I: Retrieving libss2 1.43.4-2 >>>>> I: Validating libss2 1.43.4-2 >>>>> I: Retrieving findutils 4.6.0+git+20161106-2 >>>>> I: Validating findutils 4.6.0+git+20161106-2 >>>>> I: Retrieving gcc-6-base 6.3.0-18+deb9u1 >>>>> I: Validating gcc-6-base 6.3.0-18+deb9u1 >>>>> I: Retrieving libgcc1 1:6.3.0-18+deb9u1 >>>>> I: Validating libgcc1 1:6.3.0-18+deb9u1 >>>>> I: Retrieving libstdc++6 6.3.0-18+deb9u1 >>>>> I: Validating libstdc++6 6.3.0-18+deb9u1 >>>>> I: Retrieving libc-bin 2.24-11+deb9u4 >>>>> I: Validating libc-bin 2.24-11+deb9u4 >>>>> I: Retrieving libc-l10n 2.24-11+deb9u4 >>>>> I: Validating libc-l10n 2.24-11+deb9u4 >>>>> I: Retrieving libc6 2.24-11+deb9u4 >>>>> I: Validating libc6 2.24-11+deb9u4 >>>>> I: Retrieving locales 2.24-11+deb9u4 >>>>> I: Validating locales 2.24-11+deb9u4 >>>>> I: Retrieving multiarch-support 2.24-11+deb9u4 >>>>> I: Validating multiarch-support 2.24-11+deb9u4 >>>>> I: Retrieving gpgv 2.1.18-8~deb9u4 >>>>> I: Validating gpgv 2.1.18-8~deb9u4 >>>>> I: Retrieving grep 2.27-2 >>>>> I: Validating grep 2.27-2 >>>>> I: Retrieving gzip 1.6-5+b1 >>>>> I: Validating gzip 1.6-5+b1 >>>>> I: Retrieving hostname 3.18+b1 >>>>> I: Validating hostname 3.18+b1 >>>>> I: Retrieving init-system-helpers 1.48 >>>>> I: Validating init-system-helpers 1.48 >>>>> I: Retrieving libcap-ng0 0.7.7-3+b1 >>>>> I: Validating libcap-ng0 0.7.7-3+b1 >>>>> I: Retrieving libgcrypt20 1.7.6-2+deb9u3 >>>>> I: Validating libgcrypt20 1.7.6-2+deb9u3 >>>>> I: Retrieving libgpg-error0 1.26-2 >>>>> I: Validating libgpg-error0 1.26-2 >>>>> I: Retrieving libselinux1 2.6-3+b3 >>>>> I: Validating libselinux1 2.6-3+b3 >>>>> I: Retrieving libsemanage-common 2.6-2 >>>>> I: Validating libsemanage-common 2.6-2 >>>>> I: Retrieving libsemanage1 2.6-2 >>>>> I: Validating libsemanage1 2.6-2 >>>>> I: Retrieving libsepol1 2.6-2 >>>>> I: Validating libsepol1 2.6-2 >>>>> I: Retrieving lsb-base 9.20161125 >>>>> I: Validating lsb-base 9.20161125 >>>>> I: Retrieving liblz4-1 0.0~r131-2+b1 >>>>> I: Validating liblz4-1 0.0~r131-2+b1 >>>>> I: Retrieving mawk 1.3.3-17+b3 >>>>> I: Validating mawk 1.3.3-17+b3 >>>>> I: Retrieving libncursesw5 6.0+20161126-1+deb9u2 >>>>> I: Validating libncursesw5 6.0+20161126-1+deb9u2 >>>>> I: Retrieving libtinfo5 6.0+20161126-1+deb9u2 >>>>> I: Validating libtinfo5 6.0+20161126-1+deb9u2 >>>>> I: Retrieving ncurses-base 6.0+20161126-1+deb9u2 >>>>> I: Validating ncurses-base 6.0+20161126-1+deb9u2 >>>>> I: Retrieving ncurses-bin 6.0+20161126-1+deb9u2 >>>>> I: Validating ncurses-bin 6.0+20161126-1+deb9u2 >>>>> I: Retrieving libpam-modules 1.1.8-3.6 >>>>> I: Validating libpam-modules 1.1.8-3.6 >>>>> I: Retrieving libpam-modules-bin 1.1.8-3.6 >>>>> I: Validating libpam-modules-bin 1.1.8-3.6 >>>>> I: Retrieving libpam-runtime 1.1.8-3.6 >>>>> I: Validating libpam-runtime 1.1.8-3.6 >>>>> I: Retrieving libpam0g 1.1.8-3.6 >>>>> I: Validating libpam0g 1.1.8-3.6 >>>>> I: Retrieving libpcre3 2:8.39-3 >>>>> I: Validating libpcre3 2:8.39-3 >>>>> I: Retrieving perl-base 5.24.1-3+deb9u5 >>>>> I: Validating perl-base 5.24.1-3+deb9u5 >>>>> I: Retrieving sed 4.4-1 >>>>> I: Validating sed 4.4-1 >>>>> I: Retrieving sensible-utils 0.0.9+deb9u1 >>>>> I: Validating sensible-utils 0.0.9+deb9u1 >>>>> I: Retrieving login 1:4.4-4.1 >>>>> I: Validating login 1:4.4-4.1 >>>>> I: Retrieving passwd 1:4.4-4.1 >>>>> I: Validating passwd 1:4.4-4.1 >>>>> I: Retrieving libsystemd0 232-25+deb9u8 >>>>> I: Validating libsystemd0 232-25+deb9u8 >>>>> I: Retrieving libudev1 232-25+deb9u8 >>>>> I: Validating libudev1 232-25+deb9u8 >>>>> I: Retrieving sysvinit-utils 2.88dsf-59.9 >>>>> I: Validating sysvinit-utils 2.88dsf-59.9 >>>>> I: Retrieving tar 1.29b-1.1 >>>>> I: Validating tar 1.29b-1.1 >>>>> I: Retrieving tzdata 2018i-0+deb9u1 >>>>> I: Validating tzdata 2018i-0+deb9u1 >>>>> I: Retrieving libustr-1.0-1 1.0.4-6 >>>>> I: Validating libustr-1.0-1 1.0.4-6 >>>>> I: Retrieving bsdutils 1:2.29.2-1+deb9u1 >>>>> I: Validating bsdutils 1:2.29.2-1+deb9u1 >>>>> I: Retrieving libblkid1 2.29.2-1+deb9u1 >>>>> I: Validating libblkid1 2.29.2-1+deb9u1 >>>>> I: Retrieving libfdisk1 2.29.2-1+deb9u1 >>>>> I: Validating libfdisk1 2.29.2-1+deb9u1 >>>>> I: Retrieving libmount1 2.29.2-1+deb9u1 >>>>> I: Validating libmount1 2.29.2-1+deb9u1 >>>>> I: Retrieving libsmartcols1 2.29.2-1+deb9u1 >>>>> I: Validating libsmartcols1 2.29.2-1+deb9u1 >>>>> I: Retrieving libuuid1 2.29.2-1+deb9u1 >>>>> I: Validating libuuid1 2.29.2-1+deb9u1 >>>>> I: Retrieving mount 2.29.2-1+deb9u1 >>>>> I: Validating mount 2.29.2-1+deb9u1 >>>>> I: Retrieving util-linux 2.29.2-1+deb9u1 >>>>> I: Validating util-linux 2.29.2-1+deb9u1 >>>>> I: Retrieving liblzma5 5.2.2-1.2+b1 >>>>> I: Validating liblzma5 5.2.2-1.2+b1 >>>>> I: Retrieving zlib1g 1:1.2.8.dfsg-5 >>>>> I: Validating zlib1g 1:1.2.8.dfsg-5 >>>>> I: Chosen extractor for .deb packages: dpkg-deb >>>>> I: Extracting libacl1... >>>>> I: Extracting libattr1... >>>>> I: Extracting libaudit-common... >>>>> I: Extracting libaudit1... >>>>> I: Extracting base-files... >>>>> I: Extracting base-passwd... >>>>> I: Extracting bash... >>>>> I: Extracting libbz2-1.0... >>>>> I: Extracting libdebconfclient0... >>>>> I: Extracting coreutils... >>>>> I: Extracting dash... >>>>> I: Extracting libdb5.3... >>>>> I: Extracting debconf... >>>>> I: Extracting debianutils... >>>>> I: Extracting diffutils... >>>>> I: Extracting dpkg... >>>>> I: Extracting e2fslibs... >>>>> I: Extracting e2fsprogs... >>>>> I: Extracting libcomerr2... >>>>> I: Extracting libss2... >>>>> I: Extracting findutils... >>>>> I: Extracting gcc-6-base... >>>>> I: Extracting libgcc1... >>>>> I: Extracting libc-bin... >>>>> I: Extracting libc6... >>>>> I: Extracting multiarch-support... >>>>> I: Extracting grep... >>>>> I: Extracting gzip... >>>>> I: Extracting hostname... >>>>> I: Extracting init-system-helpers... >>>>> I: Extracting libcap-ng0... >>>>> I: Extracting libgcrypt20... >>>>> I: Extracting libgpg-error0... >>>>> I: Extracting libselinux1... >>>>> I: Extracting libsemanage-common... >>>>> I: Extracting libsemanage1... >>>>> I: Extracting libsepol1... >>>>> I: Extracting lsb-base... >>>>> I: Extracting liblz4-1... >>>>> I: Extracting mawk... >>>>> I: Extracting libncursesw5... >>>>> I: Extracting libtinfo5... >>>>> I: Extracting ncurses-base... >>>>> I: Extracting ncurses-bin... >>>>> I: Extracting libpam-modules... >>>>> I: Extracting libpam-modules-bin... >>>>> I: Extracting libpam-runtime... >>>>> I: Extracting libpam0g... >>>>> I: Extracting libpcre3... >>>>> I: Extracting perl-base... >>>>> I: Extracting sed... >>>>> I: Extracting sensible-utils... >>>>> I: Extracting login... >>>>> I: Extracting passwd... >>>>> I: Extracting libsystemd0... >>>>> I: Extracting libudev1... >>>>> I: Extracting sysvinit-utils... >>>>> I: Extracting tar... >>>>> I: Extracting tzdata... >>>>> I: Extracting libustr-1.0-1... >>>>> I: Extracting bsdutils... >>>>> I: Extracting libblkid1... >>>>> I: Extracting libfdisk1... >>>>> I: Extracting libmount1... >>>>> I: Extracting libsmartcols1... >>>>> I: Extracting libuuid1... >>>>> I: Extracting mount... >>>>> I: Extracting util-linux... >>>>> I: Extracting liblzma5... >>>>> I: Extracting zlib1g... >>>>> I: Running command: chroot /work/build/tmp/work/cip-core- >>>>> armhf/isar-bootstrap-target/rootfs /debootstrap/debootstrap -- >>>>> second-stage >>>>> chroot: failed to run command ‘/debootstrap/debootstrap’: No >>>>> such file or directory >>>>> WARNING: exit code 127 from a shell command. >>>>> ERROR: Function failed: do_bootstrap (log file is located at >>>>> /work/build/tmp/work/cip-core-armhf/isar-bootstrap- >>>>> target/temp/log.do_bootstrap.316) >>>>> >>>> >>>> Looping in isar-users and Claudius. I've no idea why debootstrap >>>> should stumble here, apparently over its own feet. >>> >>> Well I would assume that it is an issue with your binfmt configuration >>> if '/work/build/tmp/work/cip-core-armhf/isar-bootstrap- >>> target/rootfs/debootstrap/deboostrap' exists. >>> >> >> 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. >> >> If that should have been the reason, we likely need a better detection >> in Isar, >> before the user runs into this non-obvious error message. >> >> Jan >> >> -- >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE >> Corporate Competence Center Embedded Linux -- 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-18 10:17 ` Claudius Heine @ 2019-03-18 10:18 ` Jan Kiszka 2019-03-19 5:18 ` akihiro27.suzuki 2019-03-19 10:14 ` Henning Schild 0 siblings, 2 replies; 15+ messages in thread From: Jan Kiszka @ 2019-03-18 10:18 UTC (permalink / raw) To: Claudius Heine, akihiro27.suzuki, isar-users, ch Cc: daniel.sangorrin, cip-dev 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). Jan > > $ cat /proc/sys/fs/binfmt_misc/qemu-arm > enabled > interpreter /usr/bin/qemu-arm-static > flags: OCF > offset 0 > magic 7f454c4601010100000000000000000002002800 > mask ffffffffffffff00fffffffffffffffffeffffff > > regards, > Claudius -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* RE: debootrap error 2019-03-18 10:18 ` Jan Kiszka @ 2019-03-19 5:18 ` akihiro27.suzuki 2019-03-19 7:22 ` Claudius Heine 2019-03-19 10:14 ` Henning Schild 1 sibling, 1 reply; 15+ messages in thread From: akihiro27.suzuki @ 2019-03-19 5:18 UTC (permalink / raw) To: jan.kiszka, claudius.heine.ext, isar-users, ch; +Cc: daniel.sangorrin, cip-dev 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? Best regards, Suzuki > -----Original Message----- > From: Jan Kiszka [mailto:jan.kiszka@siemens.com] > Sent: Monday, March 18, 2019 7:19 PM > To: Claudius Heine <claudius.heine.ext@siemens.com>; suzuki akihiro(鈴 > 木 章浩 ○ＳＷＣ□ＯＳＴ) <akihiro27.suzuki@toshiba.co.jp>; > isar-users@googlegroups.com; ch@denx.de > Cc: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) > <daniel.sangorrin@toshiba.co.jp>; cip-dev@lists.cip-project.org > Subject: Re: debootrap error > > 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,pip > e_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-ppc64 > le > >> qemu-sparc status > >> python3.5 qemu-cris qemu-mips64el qemu-riscv > 32 > >> qemu-sparc32plus > >> python3.6 qemu-hppa qemu-mipsel qemu-riscv > 64 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). > > Jan > > > > > $ cat /proc/sys/fs/binfmt_misc/qemu-arm > > enabled > > interpreter /usr/bin/qemu-arm-static > > flags: OCF > > offset 0 > > magic 7f454c4601010100000000000000000002002800 > > mask ffffffffffffff00fffffffffffffffffeffffff > > > > regards, > > Claudius > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-19 5:18 ` akihiro27.suzuki @ 2019-03-19 7:22 ` Claudius Heine 2019-03-19 7:51 ` Jan Kiszka 0 siblings, 1 reply; 15+ messages in thread From: Claudius Heine @ 2019-03-19 7:22 UTC (permalink / raw) To: akihiro27.suzuki, jan.kiszka, isar-users, ch; +Cc: daniel.sangorrin, cip-dev 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. kind regards, Claudius > > Best regards, > Suzuki > >> -----Original Message----- >> From: Jan Kiszka [mailto:jan.kiszka@siemens.com] >> Sent: Monday, March 18, 2019 7:19 PM >> To: Claudius Heine <claudius.heine.ext@siemens.com>; suzuki akihiro(鈴 >> 木 章浩 ○ＳＷＣ□ＯＳＴ) <akihiro27.suzuki@toshiba.co.jp>; >> isar-users@googlegroups.com; ch@denx.de >> Cc: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) >> <daniel.sangorrin@toshiba.co.jp>; cip-dev@lists.cip-project.org >> Subject: Re: debootrap error >> >> 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,pip >> e_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-ppc64 >> le >>>> qemu-sparc status >>>> python3.5 qemu-cris qemu-mips64el qemu-riscv >> 32 >>>> qemu-sparc32plus >>>> python3.6 qemu-hppa qemu-mipsel qemu-riscv >> 64 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). >> >> Jan >> >>> >>> $ cat /proc/sys/fs/binfmt_misc/qemu-arm >>> enabled >>> interpreter /usr/bin/qemu-arm-static >>> flags: OCF >>> offset 0 >>> magic 7f454c4601010100000000000000000002002800 >>> mask ffffffffffffff00fffffffffffffffffeffffff >>> >>> regards, >>> Claudius >> >> -- >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE >> Corporate Competence Center Embedded Linux > -- 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-19 7:22 ` Claudius Heine @ 2019-03-19 7:51 ` Jan Kiszka 2019-03-19 8:01 ` Claudius Heine 0 siblings, 1 reply; 15+ messages in thread From: Jan Kiszka @ 2019-03-19 7:51 UTC (permalink / raw) To: Claudius Heine, akihiro27.suzuki, isar-users, ch Cc: daniel.sangorrin, cip-dev 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. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-19 7:51 ` Jan Kiszka @ 2019-03-19 8:01 ` Claudius Heine 2019-03-19 9:09 ` Jan Kiszka 0 siblings, 1 reply; 15+ messages in thread From: Claudius Heine @ 2019-03-19 8:01 UTC (permalink / raw) To: Jan Kiszka, akihiro27.suzuki, isar-users, ch; +Cc: daniel.sangorrin, cip-dev 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 :) ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-19 8:01 ` Claudius Heine @ 2019-03-19 9:09 ` Jan Kiszka 2019-03-19 9:26 ` Claudius Heine 0 siblings, 1 reply; 15+ messages in thread From: Jan Kiszka @ 2019-03-19 9:09 UTC (permalink / raw) To: Claudius Heine, akihiro27.suzuki, isar-users, ch Cc: daniel.sangorrin, cip-dev 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). 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 -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-19 9:09 ` Jan Kiszka @ 2019-03-19 9:26 ` Claudius Heine 2019-03-19 9:45 ` Jan Kiszka 0 siblings, 1 reply; 15+ messages in thread From: Claudius Heine @ 2019-03-19 9:26 UTC (permalink / raw) To: Jan Kiszka, akihiro27.suzuki, isar-users, ch; +Cc: daniel.sangorrin, cip-dev 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-19 9:26 ` Claudius Heine @ 2019-03-19 9:45 ` Jan Kiszka 0 siblings, 0 replies; 15+ messages in thread From: Jan Kiszka @ 2019-03-19 9:45 UTC (permalink / raw) To: Claudius Heine, akihiro27.suzuki, isar-users, ch Cc: daniel.sangorrin, cip-dev On 19.03.19 10:26, Claudius Heine wrote: > > > 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... > Checked, this seems to work (lesson learned: never create a test entry in binfmt_misc with magic:mask of 0:0). Will write a kas patch. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-18 10:18 ` Jan Kiszka 2019-03-19 5:18 ` akihiro27.suzuki @ 2019-03-19 10:14 ` Henning Schild 2019-03-19 10:27 ` Jan Kiszka 1 sibling, 1 reply; 15+ messages in thread From: Henning Schild @ 2019-03-19 10:14 UTC (permalink / raw) To: [ext] Jan Kiszka Cc: Claudius Heine, akihiro27.suzuki, isar-users, ch, daniel.sangorrin, cip-dev 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@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. Henning > Jan > > > > > $ cat /proc/sys/fs/binfmt_misc/qemu-arm > > enabled > > interpreter /usr/bin/qemu-arm-static > > flags: OCF > > offset 0 > > magic 7f454c4601010100000000000000000002002800 > > mask ffffffffffffff00fffffffffffffffffeffffff > > > > regards, > > Claudius > ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: debootrap error 2019-03-19 10:14 ` Henning Schild @ 2019-03-19 10:27 ` Jan Kiszka 0 siblings, 0 replies; 15+ messages in thread From: Jan Kiszka @ 2019-03-19 10:27 UTC (permalink / raw) To: Henning Schild Cc: Claudius Heine, akihiro27.suzuki, isar-users, ch, daniel.sangorrin, cip-dev 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@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 ^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2019-03-19 10:27 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <HK0PR01MB297958B4B49D80F30DD800D9E24B0@HK0PR01MB2979.apcprd01.prod.exchangelabs.com>
[not found] ` <OSAPR01MB37633BA45B40D16877229C51D04B0@OSAPR01MB3763.jpnprd01.prod.outlook.com>
[not found] ` <375b3b16-8688-6fb2-4d4b-fc130c501c7e@siemens.com>
[not found] ` <TY2PR01MB5146389CBF352FDC6F104262D9440@TY2PR01MB5146.jpnprd01.prod.outlook.com>
[not found] ` <cc3ea2e6-79d9-ed10-f1a3-cf615c3e6ec8@siemens.com>
[not found] ` <TY2PR01MB514615FB285AF43385A49493D9470@TY2PR01MB5146.jpnprd01.prod.outlook.com>
2019-03-18 9:05 ` debootrap error (was: Re: [cip-dev] CIP IRC weekly meeting today) Jan Kiszka
2019-03-18 9:11 ` Claudius Heine
2019-03-18 9:39 ` debootrap error Jan Kiszka
2019-03-18 10:14 ` akihiro27.suzuki
2019-03-18 10:17 ` Claudius Heine
2019-03-18 10:18 ` Jan Kiszka
2019-03-19 5:18 ` akihiro27.suzuki
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 is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox