Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

qemu not detected - xenial env in systemd-nspawn

Featured Replies

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]

Would just like to bump this topic, as I'm wondering if there is anyone who knows how to, or has managed to get around the "Unable to find free loop device err" or the "mknod: /dev/loop0: Operation not permitted" errors?? As far as I can remember, this only becomes an issues when doing a full image... due to the use of debootstrap. As the OP has pointed out, the --capability=CAP_MKNOD appears to have no effect. This was on Ubuntu 16.04.2 / x64.

1 hour ago, nour said:

I'm running a Linux Mint 18 (so a Ubuntu)


Linux Mint "Ubuntu" might be different enough to cause troubles. IDK. If you like to discover them, go ahead, while if you want to make use of a build system, pay attention to the documentation:
 

https://docs.armbian.com/Developer-Guide_Build-Preparation/

The only supported compilation environment is Ubuntu Bionic 18.04 x64 (no other releases are supported! It has to be exactly 18.04 otherwise default compiler versions might not match so if you’re on an older Ubuntu release upgrade to 18.04 now, if you use a newer Ubuntu version start with 18.04 from scratch),

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.