networkd doesn't provide DNS to nspawn containers
Bug #1950496 reported by
Dan Streetman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Focal |
Incomplete
|
Low
|
Unassigned | ||
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
| Changed in systemd (Ubuntu Focal): | |
| assignee: | nobody → Dan Streetman (ddstreet) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
Revision history for this message
| Dan Streetman (ddstreet) wrote | #1 |
| Changed in systemd (Ubuntu Focal): | |
| assignee: | Dan Streetman (ddstreet) → nobody |
| importance: | Medium → Low |
| status: | In Progress → New |
Revision history for this message
| Dan Streetman (ddstreet) wrote | #2 |
| Changed in systemd (Ubuntu Focal): | |
| status: | New → Incomplete |
| Changed in systemd (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
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.