Open Psychesnet opened 1 year ago
At a glance, it looks like a binfmt/qemu issue - the docket container isn't able to run arm binaries. Can you post that debootstrap.log file?
It looks like that's where it initially failed and because you're not doing a clean build, it sees that there are files there already and doesn't try to run debootstrap again. Since the rest of the build doesn't see the files that should be there, it fails on future runs.
Hi @XECDesign
Thanks for replying so quickly.
I remove whole folder and git clone again, then ./build-docker.sh to try, I don't see debootstrap.log What should I do to have the log file? Thanks.
root@36869b33627e:/pi-gen# find . -name *.log
./work/KioskPi/build.log
./work/KioskPi/stage2/rootfs/var/log/bootstrap.log
./work/KioskPi/stage2/rootfs/var/log/apt/term.log
./work/KioskPi/stage2/rootfs/var/log/apt/history.log
./work/KioskPi/stage2/rootfs/var/log/alternatives.log
./work/KioskPi/stage2/rootfs/var/log/dpkg.log
./work/KioskPi/stage1/rootfs/var/log/bootstrap.log
./work/KioskPi/stage1/rootfs/var/log/apt/term.log
./work/KioskPi/stage1/rootfs/var/log/apt/history.log
./work/KioskPi/stage1/rootfs/var/log/alternatives.log
./work/KioskPi/stage1/rootfs/var/log/dpkg.log
./work/KioskPi/stage0/rootfs/var/log/bootstrap.log
./work/KioskPi/stage0/rootfs/var/log/apt/term.log
./work/KioskPi/stage0/rootfs/var/log/apt/history.log
./work/KioskPi/stage0/rootfs/var/log/alternatives.log
./work/KioskPi/stage0/rootfs/var/log/dpkg.log
./work/KioskPi/stage5/rootfs/usr/share/doc/python3.9/pybench.log
./work/KioskPi/stage5/rootfs/usr/share/doc/openjdk-11-jre-headless/test-armhf/jtreg_output-hotspot.log
./work/KioskPi/stage5/rootfs/var/log/bootstrap.log
./work/KioskPi/stage5/rootfs/var/log/apt/term.log
./work/KioskPi/stage5/rootfs/var/log/apt/history.log
./work/KioskPi/stage5/rootfs/var/log/alternatives.log
./work/KioskPi/stage5/rootfs/var/log/dpkg.log
./work/KioskPi/stage5/rootfs/var/log/fontconfig.log
./work/KioskPi/stage4/rootfs/usr/share/doc/python3.9/pybench.log
./work/KioskPi/stage4/rootfs/var/log/bootstrap.log
./work/KioskPi/stage4/rootfs/var/log/apt/term.log
./work/KioskPi/stage4/rootfs/var/log/apt/history.log
./work/KioskPi/stage4/rootfs/var/log/alternatives.log
./work/KioskPi/stage4/rootfs/var/log/dpkg.log
./work/KioskPi/stage4/rootfs/var/log/fontconfig.log
./work/KioskPi/stage3/rootfs/var/log/bootstrap.log
./work/KioskPi/stage3/rootfs/var/log/apt/term.log
./work/KioskPi/stage3/rootfs/var/log/apt/history.log
./work/KioskPi/stage3/rootfs/var/log/alternatives.log
./work/KioskPi/stage3/rootfs/var/log/dpkg.log
./work/KioskPi/stage3/rootfs/var/log/fontconfig.log
bootstrap failed: please check /pi-gen/work/KioskPi/stage0/debootstrap.log
If you saw that line, then I don't see how the log could not be there: https://github.com/RPi-Distro/pi-gen/blob/2023-05-03-raspios-bullseye/scripts/common#L24
The presence of all those other log files seems to suggest the build may have gotten further?
Hi @XECDesign
Thanks. I will check it later.
Hi pi-gen,
I try to clone repo and try to build my own image, It always fails to strange part. I just clone repo and run build-docker.sh and the error log are
Anyone can help? Thanks.