I was able to reproduce this when my bare metal system was running
focal, but I since have upgraded to impish and now i can't reproduce
this problem in a focal VM, so probably there is some specific network
setup required to reproduce (that I have on my bare metal system but not
in a VM); since it's no longer a problem for me as I've upgraded to
impish, I'm dropping ownership of this, but if anyone else has this
problem (i.e. can reproduce it) please reopen the bug and/or add a
comment.
** Changed in: systemd (Ubuntu Focal)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: systemd (Ubuntu Focal)
Importance: Medium => Low
** Changed in: systemd (Ubuntu Focal)
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1950496
Title:
networkd doesn't provide DNS to nspawn containers
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Incomplete
Bug description:
[impact]
the host networkd doesn't include DNS info to nspawn containers
[test case]
create/start a nspawn container, e.g. with 'machinectl start', open a
shell in the container, and check resolvectl to see if a nameserver
was provided.
[regression potential]
failures in the host networkd, possibly affecting other host
interfaces which are controlled by networkd, or (more likely) failure
to provide dhcp to nspawn containers
[scope]
TBD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950496/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
