Bug#923395: lxc: LXC container creation fails due to config file parse error

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#923395: lxc: LXC container creation fails due to config file parse error

Christoph Döpmann
Package: lxc
Version: 1:3.1.0+really3.0.3-4
Severity: important

Dear Maintainer,

I just freshly installed the abovementioned LXC version (none was
installed before).
When trying to create a simple container, I am experiencing the
following issue:

   $ sudo lxc-create -t debian -n testcon -- -r buster
   lxc-create: testcon: parse.c: lxc_file_for_each_line_mmap: 142 Failed
to parse config file "/etc/lxc/default.conf" at line "lxc.net.type =
empty"
   lxc-create: testcon: parse.c: lxc_file_for_each_line_mmap: 142 Failed
to parse config file "/var/lib/lxc/testcon/config" at line "lxc.net.type
= empty"
   lxc-create: testcon: tools/lxc_create.c: main: 327 Failed to create
container testcon

If I replace "lxc.net.type = empty" by "lxc.net.0.type = empty" in
/etc/lxc/default.conf, everything works out fine.


-- System Information:
Debian Release: buster/sid
   APT prefers testing
   APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lxc depends on:
ii  debconf [debconf-2.0]  1.5.70
ii  libc6                  2.28-6
ii  libcap2                1:2.25-2
ii  libgnutls30            3.6.6-2
ii  liblxc1                1:3.1.0+really3.0.3-4
ii  libseccomp2            2.3.3-3
ii  libselinux1            2.8-1+b1
ii  lsb-base               10.2018112800

Versions of packages lxc recommends:
ii  bridge-utils                 1.6-2
ii  debootstrap                  1.0.114
ii  dirmngr                      2.2.12-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1
ii  gnupg                        2.2.12-1
ii  iproute2                     4.20.0-2
ii  iptables                     1.8.2-3
ii  libpam-cgfs                  1:3.1.0+really3.0.3-4
ii  lxc-templates                3.0.3-1
ii  lxcfs                        3.0.3-2
ii  nftables                     0.9.0-2
ii  openssl                      1.1.1a-1
ii  rsync                        3.1.3-5
ii  uidmap                       1:4.5-1.1

Versions of packages lxc suggests:
ii  apparmor     2.13.2-7
ii  btrfs-progs  4.20.1-1
ii  lvm2         2.03.02-2
pn  python3-lxc  <none>

-- debconf information:
   lxc/auto_update_config:

Reply | Threaded
Open this post in threaded view
|

Bug#923395: this worked for me

Paolo Greppi
Hi Christof,

this worked for me:

cat /etc/default/lxc-net
USE_LXC_BRIDGE="true"

cat /etc/lxc/default.conf
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1

and don't forget to start the lxc-net service before starting any container:

sudo systemctl start lxc-net

Paolo

Reply | Threaded
Open this post in threaded view
|

Bug#923395: this worked for me

Christoph Döpmann
Hi Paolo,

sure, thank you. However, I would consider it a bug that the
configuration shipped by default results in a **parse error**. My
expectation would have been to just have a working container without
networking, which probably was the intention of setting "type = empty".
I guess a simple container should be **creatable** using the default
configuration.

Best,
Christoph