Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docker build fails: /bin/bash misisng in chroot #2136

Closed
Legogris opened this issue Aug 6, 2020 · 15 comments
Closed

Docker build fails: /bin/bash misisng in chroot #2136

Legogris opened this issue Aug 6, 2020 · 15 comments

Comments

@Legogris
Copy link
Contributor

Legogris commented Aug 6, 2020 •
edited

Trying to Docker build bullseye for odroidc4 fails.

Version: Recent master (b4e23b5b6a4ac679d07765ddc057562adb9f223b)

$ ./compile.sh docker BOARD=odroidc4 BRANCH=current CLEAN_LEVEL='make,debs,cache,sources' BUILD_DESKTOP=no RELEASE=bullseye

[ o.k. ] Using config file [ /home/legogris/dev/armbian/build/userpatches/config-docker.conf ]
[ .... ] Using existed a armbian Docker container
[ o.k. ] Running the container
[ o.k. ] Using config file [ /root/armbian/userpatches/config-example.conf ]
[ o.k. ] Command line: setting BOARD to [ odroidc4 ]
[ o.k. ] Command line: setting BRANCH to [ current ]
[ o.k. ] Command line: setting BUILD_DESKTOP to [ no ]
[ o.k. ] Command line: setting RELEASE to [ bullseye ]

[ dialog ] Full OS image for flashing
[ dialog ] Standard image with console interface
[...]
[ warn ] apt-cacher is disabled in containers, set NO_APT_CACHER=no to override
[...]
[ o.k. ] Merging and packaging linux firmware [ @host ]
[ o.k. ] Checking git sources [ armbian-firmware-git master ]
[ .... ] Up to date
[ o.k. ] Checking git sources [ linux-firmware-git master ]
[ .... ] Up to date
[ o.k. ] Creating board support package [ odroidc4 current ]
[ .... ] Fingerprinting
[ o.k. ] Building package [ linux-bullseye-root-current-odroidc4 ]
[ o.k. ] Building desktop package [ armbian-bullseye-desktop_20.08.0-trunk_all ]
[ o.k. ] Starting rootfs and image building process for [ odroidc4 bullseye ]
[ o.k. ] Checking for local cache [ bullseye-cli-arm64.ab3...cad.tar.lz4 ]
[ o.k. ] Extracting bullseye-cli-arm64.ab3...cad.tar.lz4 [ 0 days old ]
[ .... ] bullseye-cli-arm64.ab3...cad.tar.lz4:  469MiB [ 240MiB/s] [==========================================================================================================================================>] 100%
[ o.k. ] Adding Armbian repository and authentication key [ /etc/apt/sources.list.d/armbian.list ]
chroot: failed to run command ‘/bin/bash’: No such file or directory
[ o.k. ] Applying distribution specific tweaks for [ bullseye ]
[ o.k. ] Applying common tweaks
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
[ .... ] Installing [ linux-u-boot-current-odroidc4_20.08.0-trunk_arm64.deb ]
[ .... ] Installing [ linux-image-current-meson64_20.08.0-trunk_arm64.deb ]
[ .... ] Installing [ linux-dtb-current-meson64_20.08.0-trunk_arm64.deb ]
[ .... ] Installing [ armbian-firmware_20.08.0-trunk_all.deb ]
[ .... ] Installing [ armbian-config_20.08.0-trunk_all.deb ]
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
[ o.k. ] Enabling serial console [ ttyAML0 ]
cp: cannot stat '/root/armbian/.tmp/rootfs-current-odroidc4-bullseye-no-no/etc/armbian-release': No such file or directory
[ o.k. ] Building kernel splash logo [ bullseye ]
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
chroot: failed to run command ‘/bin/bash’: No such file or directory
[ .... ] Installing additional packages [ EXTERNAL_NEW ]
chroot: failed to run command ‘/bin/bash’: No such file or directory
[ o.k. ] Calling image customization script [ customize-image.sh ]
chroot: failed to run command ‘/bin/bash’: No such file or directory
[ error ] ERROR in function customize_image [ image-helpers.sh:119 ]
[ error ] customize-image.sh exited with error (rc: 127)
[ o.k. ] Process terminated
[ o.k. ] Unmounting [ /root/armbian/.tmp/rootfs-current-odroidc4-bullseye-no-no/ ]
[ error ] ERROR in function unmount_on_exit [ image-helpers.sh:66 ]
[ error ] debootstrap-ng was interrupted
[ o.k. ] Process terminated

No other notable warnings or errors in stderr or stdout.
@igorpecovnik
Copy link
Member

You have something wrong with your Docker installation. I just checked on my workstation, where I didn't have any Docker install, and things works. Since I use latest Linux mint, auto installer wasn't successful. Remove container and do it again:

./compile.sh dockerpurge

igorpecovnik added a commit that referenced this issue Aug 6, 2020
@igorpecovnik
Improve Docker installation support for Linux Mint
3100b44 
#2136
@Legogris
Copy link
Contributor Author

Legogris commented Aug 6, 2020

@igorpecovnik Doing this bullseye doesn't show up as an option and dockerpurge seems to ignore the RELEASE arg - maybe I'm missing something?

@igorpecovnik
Copy link
Member

Doing this bullseye doesn't show up as an option

Because Bullseye is not yet supported and is only available for developers. Add EXPERT="yes" parameter.

dockerpurge is here only to kill docker container which you can also do manually. You have to delete Armbian Docker image somehow since the one you have looks broken.

maybe I'm missing something?

https://docs.armbian.com/Developer-Guide_Build-Options/#hidden-options-for-advanced-users-default-values-are-marked-bold

@Legogris
Copy link
Contributor Author

Legogris commented Aug 6, 2020

@igorpecovnik

Got it. Same result, made sure no armbian-related images or containers existed before trying again.

@igorpecovnik
Copy link
Member

What is your host system? And can you start from a clean git clone that no caches exits.

@Legogris
Copy link
Contributor Author

Legogris commented Aug 6, 2020

@igorpecovnik I just did, and same results there as well.

Arch Linux.

Linux kernel 5.7.11-arch1-1 on x86_64.

$ docker version
Client:
 Version:           19.03.12-ce
 API version:       1.40
 Go version:        go1.14.5
 Git commit:        48a66213fe
 Built:             Sat Jul 18 01:33:21 2020
 OS/Arch:           linux/amd64
 Experimental:      true

Server:
 Engine:
  Version:          19.03.12-ce
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.14.5
  Git commit:       48a66213fe
  Built:            Sat Jul 18 01:32:59 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.3.4.m
  GitCommit:        d76c121f76a5fc8a462dc64594aea72fe18e1178.m
 runc:
  Version:          1.0.0-rc91
  GitCommit:        24a3cf88a7ae5f4995f6750654c0e2ca61ef4bb2
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Stupid question, but without looking through the script very closely, shouldn't all this be done in docker and therefore host environment shouldn't have an impact apart from cpu arch? What other things can vary that I should consider checking?

@igorpecovnik
Copy link
Member

What other things can vary that I should consider checking?

Did you try to build something else, like Bionic or Focal?

@Legogris
Copy link
Contributor Author

Legogris commented Aug 6, 2020 •
edited

@igorpecovnik Get the same for buster and bionic. Could it be qemu-related perhaps?

@igorpecovnik
Copy link
Member

Running low on ideas ... In case Docker under random Linux doesn't work -> full virtualisation would be by far fastest method.

@Legogris
Copy link
Contributor Author

Legogris commented Aug 7, 2020

Same commit and config builds fine in vagrant, never figure out what was going on in Docker. Cheers @igorpecovnik

@sjthearts
Copy link

sjthearts commented Oct 29, 2020 •
edited

@igorpecovnik I am experiencing this issue on Ubuntu 20 VM on MacOS Parallels. I am debugging, but do you have any specific diagnostic requests?

I clone the repo, patch configs, and build with ./compile.sh BOARD=espressobin BRANCH=current RELEASE=focal BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no COMPRESS_OUTPUTIMAGE=sha,gpg,img

Using the docker option I hit the same error as originally reported, in the same spot.

@EvilOlaf
Copy link
Member

Just curios. Why do you need/use NO_HOST_CHECK=yes when using a virtual machine with Focal? Does the compilation abort without it?

@sjthearts
Copy link

I pasted from the wrong window, problem in chair. Edited.

@EvilOlaf
Copy link
Member

Ah well...
Anyways. Using Parallels is mostly pretty close to using virtulabox to emulate a native environment which makes this odd...
Two things I remember. Ubuntu somtimes installing a "cloud" linux image which is missing binmft kernel module. Workaround is making sure to use a "generic" kernel image.
The other thing I like to mention is the output/debug/ folder which contains all information collected during building including errors. Start digging there.

@EvilOlaf
Copy link
Member

Assuming solved.

useful64 pushed a commit to useful64/build that referenced this issue Feb 4, 2022
@igorpecovnik
Improve Docker installation support for Linux Mint
f88ac27 
armbian#2136
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Legogris @EvilOlaf @igorpecovnik @sjthearts