Comment # 9 on bug 1177461 from Fabian Vogt

(In reply to Thomas Blume from comment #8)
> (In reply to Fabian Vogt from comment #7)
> > > The installation of those network service files seems to be bound to the
> > > inclusion of either the nfs or the cifs module:
> > > 
> > > -->
> > > # grep -r 'etc/protocol' /usr/lib/dracut/modules.d/
> > > grep: /usr/lib/dracut/modules.d/30ignition/ignition: binary file matches
> > > /usr/lib/dracut/modules.d/95cifs/module-setup.sh:    inst_multiple
> > > /etc/services /etc/nsswitch.conf /etc/protocols
> > > /usr/lib/dracut/modules.d/95nfs/module-setup.sh:    inst_multiple
> > > /etc/services /etc/nsswitch.conf /etc/rpc /etc/protocols /etc/idmapd.conf
> > > --<
> > > 
> > > Are these modules getting included in the test?
> > 
> > It still uses the initrd generated by kiwi at that point, which is built
> > with "--no-hostonly". As nfs tools are available, it includes the nfs dracut
> > module as well.
> 
> Hi Fabian, how should we go on here?
> I guess we'd either need to exclude the nfs dracut module when creating the
> initrd in kiwi or we need to include the necessary files.

Why not both?

That the nfs module doesn't work because files are missing is a dracut bug,
even one where the fix should be relatively simple. Avoiding the nfs module in
kiwi generated initrds would only be a workaround.

> However, if the nfs module isn't really needed, I'd vote to omit it when
> building the initrd for the image.
> But I'm not sure how this could be addressed from within dracut.
> Any idea?

That would be something for kiwi AFAICT, just explicitly omitting some modules,
or somehow avoiding --no-hostonly. kiwi supports booting live images over the
network though, so it might actually be intentional that nfs is included.