systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxd |
Fix Released
|
Unknown
|
|||
systemd |
Fix Released
|
Unknown
|
|||
apparmor (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
lxd (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
systemd (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
Bug Description
This is a regression from 239-7ubuntu15 to 240-5ubuntu1.
Steps to reproduce:
lxc launch ubuntu-daily:disco rbasak-resolv
lxc exec rbasak-resolv bash
systemctl status systemd-resolved # observe running
echo "deb http://
apt update
# Update to 240-5ubuntu1 from proposed
apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd
reboot
lxc exec rbasak-resolv bash
systemctl status systemd-resolved # observe failed
● systemd-
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago
Docs: man:systemd-
https:/
https:/
https:/
Process: 290 ExecStart=
Main PID: 290 (code=exited, status=
Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-
Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-
Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution.
Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-
Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-
Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution.
This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working.
In my case it breaks "autopkgtest -U --apt-pocket=
Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently).
=== Workaround ===
$ lxc config set test-v240 raw.apparmor 'mount options=
mount options=
mount options=
mount options=
mount options=
description: | updated |
Changed in systemd (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in apparmor (Ubuntu): | |
status: | New → Invalid |
Changed in lxd (Ubuntu): | |
status: | New → Confirmed |
Changed in lxd: | |
status: | Unknown → New |
Changed in systemd: | |
status: | Unknown → Fix Released |
Changed in systemd (Ubuntu): | |
status: | Invalid → In Progress |
Changed in systemd (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in lxd: | |
status: | New → Fix Released |
Changed in lxd (Ubuntu): | |
status: | Confirmed → Invalid |
If it matters, my host is running Disco, upgraded nightly but last rebooted 59 days ago. lxd is from the snap:
installed: 3.9 (9919) 54MB -