New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
systemd-nspawn uses hard-coded location for resolv.conf #7302
Comments
Seems it's hard-coded in a few other places as well:
|
hmm, where's resolved itself installed on such systems? if it's in /usr/lib, then i figure its resolv.conf should also be in /usr/lib, and we should change rootlibexecdir → libexecdir here... |
@poettering resolved is installed to roolibexecdir: https://github.com/systemd/systemd/blob/master/meson.build#L1420
https://github.com/systemd/systemd/blob/master/src/resolve/meson.build#L139
|
hmm, ok. an i figure that's because networkd can run in early boot too... maybe we should leave it that way then. Anyway, a patch that fixes the resolv.conf path for split-usr systems would be greatly appreciated. |
At https://github.com/systemd/systemd/blob/master/src/nspawn/nspawn.c#L1413 we hard-code the location for the system installed resolv.conf and check for /usr/lib/systemd/resolv.conf
For split-usr systems, resolv.conf is not installed at /usr though, but /lib/systemd/resolv.conf:
https://github.com/systemd/systemd/blob/master/src/resolve/meson.build#L140 (rootlibexecdir)
The text was updated successfully, but these errors were encountered: