- Dropped my special KVM-LXD profile that I usually use - Spawned a new Bionic container # working - upgraded to systemd of cosmic Right on upgrade I get the breakage: The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 307 not upgraded. Need to get 3404 kB of archives. After this operation, 470 kB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libnss-systemd amd64 239-7ubuntu4 [111 kB] Get:2 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libpam-systemd amd64 239-7ubuntu4 [114 kB] Get:3 http://archive.ubuntu.com/ubuntu cosmic/main amd64 systemd amd64 239-7ubuntu4 [2967 kB] Get:4 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libsystemd0 amd64 239-7ubuntu4 [214 kB] Fetched 3404 kB in 1s (4342 kB/s) (Reading database ... 28491 files and directories currently installed.) Preparing to unpack .../libnss-systemd_239-7ubuntu4_amd64.deb ... Unpacking libnss-systemd:amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ... Preparing to unpack .../libpam-systemd_239-7ubuntu4_amd64.deb ... Unpacking libpam-systemd:amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ... Preparing to unpack .../systemd_239-7ubuntu4_amd64.deb ... Unpacking systemd (239-7ubuntu4) over (237-3ubuntu10.3) ... Preparing to unpack .../libsystemd0_239-7ubuntu4_amd64.deb ... Unpacking libsystemd0:amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (239-7ubuntu4) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (239-7ubuntu4) ... Installing new version of config file /etc/systemd/journald.conf ... Installing new version of config file /etc/systemd/logind.conf ... Installing new version of config file /etc/systemd/resolved.conf ... Installing new version of config file /etc/systemd/system.conf ... Warning: The unit file, source configuration file or drop-ins of systemd-networkd.service changed on disk. Run 'systemctl daemon-reload' to reload units. Warning: Stopping systemd-networkd.service, but it can still be activated by: systemd-networkd.socket Warning: The unit file, source configuration file or drop-ins of systemd-resolved.service changed on disk. Run 'systemctl daemon-reload' to reload units. Job for systemd-resolved.service failed because the control process exited with error code. See "systemctl status systemd-resolved.service" and "journalctl -xe" for details. dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 1 Processing triggers for man-db (2.8.3-2) ... Processing triggers for dbus (1.12.2-1ubuntu1) ... dpkg: dependency problems prevent configuration of libnss-systemd:amd64: libnss-systemd:amd64 depends on systemd (= 239-7ubuntu4); however: Package systemd is not configured yet. dpkg: error processing package libnss-systemd:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libpam-systemd:amd64: libpam-systemd:amd64 depends on systemd (= 239-7ubuntu4); however: Package systemd is not configured yet. dpkg: error processing package libpam-systemd:amd64 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: systemd libnss-systemd:amd64 libpam-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) root@b-systemd:~# systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-08-29 10:55:44 UTC; 19s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 819 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=217/USER) Main PID: 819 (code=exited, status=217/USER) Aug 29 10:55:44 b-systemd systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Aug 29 10:55:44 b-systemd systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Aug 29 10:55:44 b-systemd systemd[1]: Stopped Network Name Resolution. Aug 29 10:55:44 b-systemd systemd[1]: systemd-resolved.service: Start request repeated too quickly. Aug 29 10:55:44 b-systemd systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Aug 29 10:55:44 b-systemd systemd[1]: Failed to start Network Name Resolution.