Then OTOH on a Fresh Cosmic VM it works to spawn a cosmic container.
ubuntu@c-systemd:~$ lxc launch ubuntu-daily:cosmic/amd64 c
Creating c
Starting c
ubuntu@c-systemd:~$ lxc exec c bash
root@c:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled;
vendor preset: enabled)
Active: active (running) since Wed 2018-08-29 11:15:16 UTC; 29s 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
Main PID: 152 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 1152)
Memory: 6.5M
CGroup: /system.slice/systemd-resolved.service
└─152 /lib/systemd/systemd-resolved
Aug 29 11:15:16 c systemd[1]: Starting Network Name Resolution...
Aug 29 11:15:16 c systemd-resolved[152]: Positive Trust Anchors:
Aug 29 11:15:16 c systemd-resolved[152]: . IN DS 19036 8 2
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 29 11:15:16 c systemd-resolved[152]: . IN DS 20326 8 2
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 29 11:15:16 c systemd-resolved[152]: Negative trust anchors:
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa
19.172.in-addr.arpa 20.172.in
Aug 29 11:15:16 c systemd-resolved[152]: Using system hostname 'c'.
Aug 29 11:15:16 c systemd[1]: Started 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
