Builds fail on RPi 3B+ with Buster #294
Comments
|
Not sure why your build continues. Mine fails with bootstrap. If I recall correctly, debootstrap doesn't like running through capsh. Since it's not important during the bootstrap stage, we can just remove it, but it would be nice to know what the actual issue is. |
|
I also got this error when using the docker build.... |
|
Nope, still fails with missing folders / files during the export phase. |
|
The problem definitely seemed to be capsh for me. The build seems to be working since I replaced with just |
|
Hmm yep, that works for me too, thanks. |
|
It looks like this workaround breaks the APT proxy option, After making the same change on my end I started getting a lot of messages reading "Unsupported proxy configured: 192.168.2.1717//3142". It's odd because I can see Pi-Gen is pulling some files from the proxy at first but then suddenly it doesn't like the proxy any more. |
|
Not working through bash was a good hint. Looks like it runs debootstrap through bash rather than sh then has compatibility issues? Not sure how to fix this properly. We need capsh because otherwise you end up with files with capabilities set which will have problems on NFS filesystems or when archived with tar. Capsh will only use bash, but will parse arguments, so |
|
@jvonau I've tried your change: #setarch linux32 capsh --drop=cap_setfcap -- "${BOOTSTRAP_CMD}" "${BOOTSTRAP_ARGS[@]}" || true ...and the build seems to work. However, I'm not sure I understand what would be the impact of this change? Could you please clarify? |
|
@smg-bg Not sure of the total impact, haven't tried booting the resulting image yet. I was looking for quick way to continue working towards a custom image farther up the chain and the above mentioned fix got me past the error I was seeing. Easy to revert when there is a proper fix. |
|
All of the images I've built with that workaround seem to work fine. |
|
Good to know, thanks |
|
I can also confirm that my custom image works fine with that fix. |
|
If you don't drop |
|
I think I have a fix here #338 (comment) |
|
I’ll test it this weekend. |
|
An alternative fix here is to pass the full path to debootstrap. (The underlying issue is that in the case that breaks, |
This fixes RPi-Distro#338 and fixes RPi-Distro#294
This fixes RPi-Distro#338 and fixes RPi-Distro#294
This fixes RPi-Distro#338 and fixes RPi-Distro#294
|
Hi @benp44 / @RussellJoyce / @dlabun / @smg-bg / @mutability, Do u guys still encounter same error "stage0/rootfs/proc: mount point does not exist." recently? If yes, can share your solution on this issue? As I encounter same error today, but latest fix by @XECDesign on 29th October 2019 is already in the scripts/common file. Here is error screenshot: Here is scripts/common file code: Thanks in advance! |
This fixes RPi-Distro#338 and fixes RPi-Distro#294
I pulled the latest copy of the pi-gen project and builds are not completing due to missing file / folder issues. I assume this must be related to the move to Buster. This was run on a RPi 3B+ with a clean copy of Raspbian I just downloaded from the RPi website.
The text was updated successfully, but these errors were encountered: