In case it wasn't clear I followed instructions for basic privileged
usage. not user namespaces.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1396536
Title:
lxc_start - Exec format
$ sudo ls -lisa /var/lib/lxc/u1/rootfs/sbin/init
541928 0 lrwxrwxrwx 1 root root 7 Nov 19 23:17 /var/lib/lxc/u1/rootfs/sbin/init
- upstart
$ sudo ls -lisa /var/lib/lxc/u1/rootfs/sbin/upstart
541969 220 -rwxr-xr-x 1 root root 223596 Nov 19 23:17
/var/lib/lxc/u1/rootfs/sbin/upstart
--
You
$ sudo file /var/lib/lxc/u1/rootfs/sbin/upstart
/var/lib/lxc/u1/rootfs/sbin/upstart: ELF 32-bit LSB shared object, ARM, EABI5
version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32,
BuildID[sha1]=401fd3761e2edac12fc6081bebbfd834a985e11b, stripped
--
You received this
No my arch is amd64, that's why I specified -a armhf.
I know about qemu (I wasn't sure whether to use static or binfmt), but errors
should be meaningful, instead it seems as if lxc is working fine, but in fact
it's not. Obviously it's not a matter of permissions, so the error is wrong.
The
I agree it'd be nice for the download template to be clever and filter
its output. However the fact that it's very very difficult to know what
your CPU is actually capable of running (especially for arm64, armel,
armhf and powerpc, powerpc64 and ppc64el) and the name for the
architectures changes