- 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)
$ 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):
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 post_start: 1265 - '/sbin/init' started with pid '13393' signal_ handler: 310 - invalid pid for SIGCHLD signal_ handler: 314 - container init process exited __lxc_start: 1207 - Container violated its seccomp policy __lxc_start: 1215 - Pushing physical nics back to host namespace __lxc_start: 1218 - Tearing down virtual network devices used by container lxc_delete_ network: 2939 - failed to remove interface '(null)' lxc_error_ set_and_ log:55 - child <13393> ended on signal (31) lxc_delete_ network: 2939 - failed to remove interface '(null)'
[..]
lxc-start 1449065480.085 NOTICE lxc_start - start.c:start:1254 - exec'ing '/sbin/init'
lxc-start 1449065480.085 NOTICE lxc_start - start.c:
lxc-start 1449065480.085 WARN lxc_start - start.c:
lxc-start 1449065480.086 DEBUG lxc_start - start.c:
lxc-start 1449065480.086 DEBUG lxc_start - start.c:
lxc-start 1449065480.086 DEBUG lxc_start - start.c:
lxc-start 1449065480.086 DEBUG lxc_start - start.c:
lxc-start 1449065480.086 WARN lxc_conf - conf.c:
lxc-start 1449065480.092 INFO lxc_error - error.c:
lxc-start 1449065480.093 WARN lxc_conf - conf.c:
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 architecture
$ sudo chroot rootfs/
# dpkg --print-
armhf
nspawn fails too, with a different error message:
$ sudo systemd-nspawn -b -D rootfs/ rootfs. rootfs/ sys/fs/ selinux: Read-only file system rootfs/ sys/fs/ selinux: Read-only file system
Spawning container rootfs on /home/ubuntu/
Press ^] three times within 1s to kill container.
Failed to create directory /home/ubuntu/
Failed to create directory /home/ubuntu/
/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 systemd/ systemd" sig=31 arch=40000028 syscall=45 compat=1 ip=0xf718fbd6 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/