ppetru/alo-cluster
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix NFS automount race.

Browse Source
This commit is contained in:
Petru
2025-10-24 08:59:27 +01:00
parent 974d10cbe2
commit b7ef5f89b7
1 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
common/nomad.nix
View File

@@ -59,7 +59,21 @@ in
extraSettingsPaths = [ "/etc/nomad-alo.json" ]; extraSettingsPaths = [ "/etc/nomad-alo.json" ];
}; };
systemd.services.nomad.wants = [ "network-online.target" ]; # Fix race condition between NFS automount and Docker bind mounts:
# Without this, Docker can bind-mount the empty automount stub directory
# before NFS actually mounts, causing permission errors and missing data.
# - RequiresMountsFor: tells systemd that Nomad depends on /data/services
# - ExecStartPre: triggers the automount before Nomad starts
# Note: boot will still succeed if NFS is unavailable (Nomad just won't start)
# TODO: NFS mount uses Consul DNS which resolves to an IP at mount time.
# If the NFS server moves to a different IP, the mount becomes stale
# and needs to be remounted. Consider using a VIP or implementing
# a health check that remounts on staleness detection.
systemd.services.nomad = {
wants = [ "network-online.target" ];
unitConfig.RequiresMountsFor = [ "/data/services" ];
serviceConfig.ExecStartPre = "${pkgs.coreutils}/bin/ls /data/services";
};
environment.etc."nomad-alo.json".text = builtins.toJSON { environment.etc."nomad-alo.json".text = builtins.toJSON {
plugin.docker.config = { plugin.docker.config = {