search

RPi-Distro / pi-gen

Tool used to create the official Raspberry Pi OS images
BSD 3-Clause "New" or "Revised" License
2.62k stars 1.64k forks source link

build-docker.sh and build.sh - grabs i386 debian image #644

Open juddy opened 1 year ago

juddy commented 1 year ago

root@debian:/home/wjk/Code/pi-gen# ./build-docker.sh Sending build context to Docker daemon 906.2kB Step 1/6 : ARG BASE_IMAGE=debian:bullseye Step 2/6 : FROM ${BASE_IMAGE} bullseye: Pulling from i386/debian 8caf426a2703: Pull complete

juddy commented 1 year ago

Steps to reproduce:

git clone --depth 1 https://github.com/RPI-Distro/pi-gen.git

Create a config file and run

sudo ./build.sh

Workaround:

git clone --depth 3 https://github.com/RPI-Distro/pi-gen.git
XECDesign commented 1 year ago

Why is this an issue and how does changing the clone depth fix it?

alexander-sony commented 1 year ago

Is it possible to build arm64/v8 images on a x86_64 host? The case "$(uname -m)" in in build-docker.sh must be there for some reason. Would it be possible to build arm64/v8 by using a WM based on Debian 32-bit?

XECDesign commented 1 year ago

Is it possible to build arm64/v8 images on a x86_64 host? The case "$(uname -m)" in in build-docker.sh must be there for some reason. Would it be possible to build arm64/v8 by using a WM based on Debian 32-bit?

I'm not sure if the 32-bit version of qemu even comes with an aarch64 user binary. But yes, I am not currently aware of any issues with building arm64 images on x64 hosts. Not sure about armv8.

I don't think the use of a 32-bit qemu or container should be required at all on Bullseye, for example.