Re: enable systemd-resolved in early boot (dracut)

[Aleksandar Kostadinov <akostadi@xxxxxxxxxx>]

Thanks a lot! It worked like a charm. Because I didn't use
systemd-networkd I had to add it manually

$ cat /etc/dracut.conf.d/resolved.conf
add_dracutmodules+=" systemd-resolved "

Now mdns resolution works during early boot (clevis vs tang).

On Thu, Mar 21, 2024 at 3:51 PM Andrei Borzenkov <arvidjaar@xxxxxxxxx> wrote:
>
> On Thu, Mar 21, 2024 at 4:44 PM Cristian Rodríguez
> <crrodriguez@xxxxxxxxxxxx> wrote:
> >
> > On Tue, Mar 19, 2024 at 7:44 AM Aleksandar Kostadinov
> > <akostadi@xxxxxxxxxx> wrote:
> > >
> > > Hello,
> > >
> > > I want to enable systemd-resolved in early boot so that `clevis` can
> > > resolve `tang` address by mdns. This will simplify local network
> > > configuration by not relying on static IP addresses.
> > >
> > > But it seems that is not enabled by default.
> > >
> > > Is there a way to tell dracut to also include and start
> > > `systemd-resolved` as part of early boot network start?
> > >
> > > Thank you.
> >
> > Please ask in the dracut lists how, systemd does not ship dracut
> > modules..now it should be pretty straightforward if there is already a
> > way to do early network.
>
> dracut already has the systemd-resolved module which is included
> automatically if you choose systemd-networkd for network management.
> systemd-networkd module is part of upstream dracut as well.
>