Quantcast
Channel: Armbian news
Viewing all articles
Browse latest Browse all 486

qemu not detected - xenial env in systemd-nspawn

$
0
0

Hi,

I'm trying to compile an Armbian image for OdroidC2 with btrfs rootfs, I created an Ubuntu Xenial container with systemd-nspawn as building environment.

The building process reports these errors:

ERROR in function prepare_partitions debootstrap-ng.sh:374 err
Unable to find free loop device  err
Process terminated  info
ERROR in function unmount_on_exit debootstrap-ng.sh:525 err
debootstrap-ng was interrupted  err
Process terminated  info

I've done a little search and found that there are no loop device in a default container and that's impossible to create a new one with:

mknod /dev/loop0 b 7 0

The answer is:

mknod: /dev/loop0: Operation not permitted

So I tried to boot the container with the option --capability=CAP_MKNOD but the answer remains the same.

 

Finally the question: there is anyone who have built Armbian in a systemd container successfully?

 

[OT]

I add another error during build process (I don't know if it is caused by the previous error)

update-binfmts: warning: qemu-arm not in database of installed binary formats.
update-binfmts: exiting due to previous errors
update-binfmts: warning: qemu-aarch64 not in database of installed binary formats.
update-binfmts: exiting due to previous errors

This cause many issues when executing ARM binary later in the process.

[/OT]


Viewing all articles
Browse latest Browse all 486

Trending Articles