Comment 21 for bug 1971935

I spent quite some time gathering information about this today, and narrowed it down to this:

if autofs is setup before nfs-common, we get the incorrect rpc_pipefs mount point. If nfs-common is setup first, then it's fine.

Furthermore, for some reason if I purge nfs-common and autofs, and reinstall, this attempt gets the "correct" ordering and the rpc_pipefs mountpoint is correct.

In Debian it's even more strange: after sudo apt install autofs, you get rpc_pipefs mounted twice: once by the generator, and once by that var-lib mount unit.

As a temporary workaround for now, I'd suggest to instead of "apt install autofs", and rely on that to pull in nfs-common, to first "apt install nfs-common", and then the rest that is needed/wanted.