Package: lxc
Version: 1:1.0.8-1
Followup-For: Bug #800699

This seems to be the same issue as
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773384 which was dismissed
with "this will never work". But it will, it's fixed in upstream, see
https://github.com/hallyn/lxc/commit/473ebc77d6762c2ec49fe59983dabc04f695fd01

Besides, it's not just launching 64b containers with 32b userspace. Currently
I can't launch any containers at all unless I manually setarch i686, otherwise
I'm getting the same errors:

lxc-start: seccomp.c: get_new_ctx: 192 Seccomp error -17 (Unknown error -17) 
adding arch: 2
lxc-start: start.c: lxc_init: 388 failed loading seccomp policy
lxc-start: start.c: __lxc_start: 1065 failed to initialize the container
lxc-start: lxc_start.c: main: 341 The container failed to start.
lxc-start: lxc_start.c: main: 345 Additional information can be obtained by 
setting the --logfile and --logpriority options.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (980, 'testing'), (980, 'stable'), (500, 'unstable-debug'), (500, 
'unstable'), (500, 'stable'), (200, 'experimental'), (1, 'experimental-debug')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.4.0-lis64+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages lxc depends on:
ii  init-system-helpers  1.24
ii  libapparmor1         2.10-2+b2
ii  libc6                2.21-6
ii  libcap2              1:2.24-12
ii  liblxc1              1:1.0.8-1
ii  libseccomp2          2.2.3-2
ii  libselinux1          2.4-3
ii  python3              3.4.3-7

Versions of packages lxc recommends:
ii  cgmanager    0.39-2
ii  debootstrap  1.0.75
ii  openssl      1.0.2e-1
ii  rsync        3.1.1-3

Versions of packages lxc suggests:
pn  lua5.2  <none>

-- no debconf information

-- 
Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/

Reply via email to