Re: Failed to run debootstrap for armhf stretch
Sorry, I should mention that I did start schroot in root mode and run
second stage, but it failed on permission denied
# /debootstrap/debootstrap --second-stage
/debootstrap/debootstrap: 1455: /debootstrap/debootstrap: cannot
create //test-dev-null: Permission denied
E: Cannot install into target '/' mounted with noexec or nodev
As I mentioned in previous message, that the host mount were shown in
the schroot environment, I was not clear that was the problem or not.
I used the same schroot mount for armhf jessie which does not show the
mount information in host environment.
On 11/5/18, Paul Wise <pabs@debian.org> wrote:
> On Mon, 2018-11-05 at 20:38 +1100, hh h wrote:
>
>> Does Extracting package means installing it?
>
> No, it just means extracting the files to disk, but not running any
> install tasks like maintainer scripts or triggers etc. The maintainer
> scripts are needed to make the install work properly. It sounds to me
> like you have used qemu-user-static but you only did the first stage
> (debootstrap --foreign) of a two-stage debootstrap. I probably should
> have explained it better before, but qemu-user-static is for when you
> want to do a single-stage debootstrap solely on amd64. The two-stage
> debootstrap (debootstrap --foreign, debootstrap --second-stage) is for
> when you are not using qemu-user-static but want to do the second stage
> on the ARM device itself. IIRC debootstrap will setup the install to do
> the right thing on the first boot of the ARM device.
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>
>
Reply to: