Multilib availability

[WarheadsSE]

You can run it on the host. Thats the nature of mkarchroot.

[evand]

Damn, this is frustrating. I don't seem to be able to set up a legitimate chroot. Here's what I've done (following guidance in this thread and https://wiki.archlinux.org/index.php/De ... ean_Chroot) using custom pacman.conf which sets the repo to armv7h:

$this->bbcode_second_pass_code('', '
CHROOT=$HOME/chroot
mkdir ~/chroot
mkarchroot -C ~/pacman.conf -c $CHROOT/cache/armv7h $CHROOT/armv7h base')

Right at the end it terminates as follows:
$this->bbcode_second_pass_code('', 'Container armv7h terminated by signal SYS.')

$this->bbcode_second_pass_code('', 'arch-chroot $CHROOT /bin/bash -l') returns:
$this->bbcode_second_pass_code('', 'mount: mount point /root/chroot/proc does not exist
==> ERROR: failed to setup chroot /root/chroot')

[evand]

$this->bbcode_second_pass_code('', 'CHROOT=$HOME/chroot/armv7h
arch-chroot $CHROOT /bin/bash -l') does however do the trick. Here's praying I can now get this lot up using nspawn

[evand]

No cigar, so tried a different approach adapting the guidance here: https://wiki.archlinux.org/index.php/Sy ... _container:
$this->bbcode_second_pass_code('', '
mkdir /armv7h
pacstrap -C ~/pacman.conf -i -G -M -d /armv7h/ base
')

Installation was successful, no error messages.

then:
$this->bbcode_second_pass_code('', 'systemd-nspawn -b -D /armv7h -n')

returns:
$this->bbcode_second_pass_code('', 'Spawning container armv7h on /armv7h.
Press ^] three times within 1s to kill container.

Container armv7h terminated by signal SYS.')

[evand]

Should I be filing a bug report re

$this->bbcode_second_pass_code('', 'mkarchroot -C pacman_armv7h.conf $CHROOT/root base-devel')

returning

$this->bbcode_second_pass_code('', 'cp: cannot stat '/etc/pacman.d/gnupg': No such file or directory
Container root terminated by signal SYS.') ?

[WarheadsSE]

I will play with the nspawn, this just happened to me as well.

[evand]

Any luck getting nspawn working?

[WarheadsSE]

I am actually seeing an issue on syscall 285, which ends up related to the kernel on the C2. I have not had a lot of spare time to troubleshoot recently however, with South East Linux Fest 2016 this coming weekend.

[evand]

Did you ever manage to come back to this, anything I can do to help get it resolved?

[WarheadsSE]

I have not, yet. Sorry. What I have found is that it ends up doing this only when using a 32-bit nspawn, however a 32-bit chroot seems to work fine.