But OTOH picking a random system - here a powerpc box and starting a
cosmic container reproduces the same issue:

cpaelzer@diamond:~$ lxc launch ubuntu-daily:c cpaelzer-cosmic-systemd
Creating cpaelzer-cosmic-systemd                                                
                                                                                
          
Starting cpaelzer-cosmic-systemd
cpaelzer@diamond:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)"
VERSION_ID="18.10"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic
cpaelzer@diamond:~$ lxc exec cpaelzer-cosmic-systemd bash
root@cpaelzer-cosmic-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 11:10:32 UTC; 1min 
15s 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: 179 ExecStart=/lib/systemd/systemd-resolved (code=exited, 
status=217/USER)
 Main PID: 179 (code=exited, status=217/USER)

Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Service has no hold-off time (RestartSec=0), scheduling restart.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Scheduled restart job, restart counter is at 5.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: Stopped Network Name 
Resolution.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Start request repeated too quickly.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Failed with result 'exit-code'.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: Failed to start Network 
Name Resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1789627

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789627/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to