Been fighting Debian #Trixie 13 for two days now. It seems to be impossible to auto mount an NFS4 share at boot. Manually it works fine.
Not even with `ro,auto,sync,default,hard,noatime,retrans=15,x-systemd.after=network-online.target,x-systemd.automount,x-systemd.requires=network-online.target,_netdev,clientaddr=
192.0.2.13` in `fstab`.
This used to work in Debian #Bookworm 12, Ubuntu jammy (22) and noble (24).
Next attempt: `autofs` or directly in OCI container
Changed my strategy, due to a race condition between systemd mounting #NFS and #docker creating bind volumes.
Trying to mount NFS directly from within a container defined as a volume. Works when deployed with #ansible, but only during runtime. At boot, the container is started before the NFS volume is ready causing the container to fail starting.
This issue is 100% reproducible and can be found online everywhere going back for years. No solution to be found.
#WTF