Hi Bastian, On Sun, Mar 19, 2023 at 12:21:48PM +0100, Bastian Blank wrote: > This modification of global configuration breaks the building of cloud > images. We need a way to install the package, but no services will run > in the environment, nor is there a systemd-resolved in the same network > namespace.
That sounds fine to me. > The build does not exhibit that failure right now, because by chance > systemd-resolved is the last thing that needs a working resolver before > the build is finished. But this is not guaranteed. On irc, you explained the concrete expectation an I'm giving it here for reference. You expect that you can install systemd-resolved without running any services or init processes (in a chroot or service-less container) and then continue using DNS resolution inside that environment. I content that such an environment is very unusual since you would not want to install systemd-resolved in a setting where you do not run services and if you are in bootstrap setting, you can use an external apt (with access to an external resolv.conf) to download packages. Even then when assuming that your expectation is well-founded (which I do not fully agree with), it remains unclear why Michael's proposal would not solve your problem. Given the lack of answers on these questions, I think that rc-severity is not reasonable though I do not have authority on this question. Helmut
