Some more obvservations:
- I get exactly the same failure with lxc launch'ing a trusty armhf instance.
- arm64 lxd images work fine (tested trusty and wily, there are no xenial ones
yet)
So I went down a level and tried with LXC:
sudo lxc-create -n x1armhf -t ubuntu -- -r xenial -a armhf
This also fails, but with some more info:
$ sudo lxc-start -n x1armhf -F -l debug -o /dev/stderr
[..]
lxc-start 1449065480.085 NOTICE lxc_start - start.c:start:1254 -
exec'ing '/sbin/init'
lxc-start 1449065480.085 NOTICE lxc_start - start.c:post_start:1265 -
'/sbin/init' started with pid '13393'
lxc-start 1449065480.085 WARN lxc_start - start.c:signal_handler:310
- invalid pid for SIGCHLD
lxc-start 1449065480.086 DEBUG lxc_start - start.c:signal_handler:314
- container init process exited
lxc-start 1449065480.086 DEBUG lxc_start - start.c:__lxc_start:1207 -
Container violated its seccomp policy
lxc-start 1449065480.086 DEBUG lxc_start - start.c:__lxc_start:1215 -
Pushing physical nics back to host namespace
lxc-start 1449065480.086 DEBUG lxc_start - start.c:__lxc_start:1218 -
Tearing down virtual network devices used by container
lxc-start 1449065480.086 WARN lxc_conf -
conf.c:lxc_delete_network:2939 - failed to remove interface '(null)'
lxc-start 1449065480.092 INFO lxc_error -
error.c:lxc_error_set_and_log:55 - child <13393> ended on signal (31)
lxc-start 1449065480.093 WARN lxc_conf -
conf.c:lxc_delete_network:2939 - failed to remove interface '(null)'
and then it exits again (with code 0!), and there is no container
running. Not sure if the "violated its seccomp policy" bit is
interesting?
So one further step down: I directly downloaded and unpacked
https://images.linuxcontainers.org/images/ubuntu/xenial/armhf/default/20151202_04:37/lxd.tar.xz:
$ sudo tar xpf lxd.tar.xz
$ sudo chroot rootfs/
# dpkg --print-architecture
armhf
nspawn fails too, with a different error message:
$ sudo systemd-nspawn -b -D rootfs/
Spawning container rootfs on /home/ubuntu/rootfs.
Press ^] three times within 1s to kill container.
Failed to create directory /home/ubuntu/rootfs/sys/fs/selinux: Read-only file
system
Failed to create directory /home/ubuntu/rootfs/sys/fs/selinux: Read-only file
system
/etc/localtime is not a symlink, not updating container timezone.
Container rootfs terminated by signal SYS.
In syslog I'm getting seccomp errors (from LXC and nspawn):
Dec 02 14:11:57 arm64-lxd-test audit[13536]: SECCOMP auid=1000 uid=0 gid=0
ses=1 pid=13536 comm="init" exe="/lib/systemd/systemd" sig=31 arch=40000028
syscall=45 compat=1 ip=0xf763abd6 code=0x0
Dec 02 14:15:03 arm64-lxd-test audit[25812]: SECCOMP auid=4294967295 uid=0
gid=0 ses=4294967295 pid=25812 comm="systemd" exe="/lib/systemd/systemd" sig=31
arch=40000028 syscall=45 compat=1 ip=0xf718fbd6 code=0x0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522026
Title:
armhf lxd container does not start on arm64 system
To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1522026/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
