From bfc12c76247856588fe3d49515bce060575d26ba Mon Sep 17 00:00:00 2001
From: Pim Kunis <pim@kunis.nl>
Date: Wed, 4 Dec 2024 22:57:37 +0100
Subject: [PATCH] Increase inotify limit for servers

---
 machines/lewis/configuration.nix |  1 -
 nixos/server.nix                 | 13 ++++++++++---
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/machines/lewis/configuration.nix b/machines/lewis/configuration.nix
index cd489d8..ea6231b 100644
--- a/machines/lewis/configuration.nix
+++ b/machines/lewis/configuration.nix
@@ -16,7 +16,6 @@
     };
 
     pim = {
-      # TODO: this should be dynamically set using Colmena tags
       k3s.serverAddr = "https://jefke.dmz:6443";
       data-sharing.enable = true;
       backups.enable = true;
diff --git a/nixos/server.nix b/nixos/server.nix
index 270bacf..10beb4e 100644
--- a/nixos/server.nix
+++ b/nixos/server.nix
@@ -29,9 +29,16 @@
       };
     };
 
-    boot.loader = {
-      systemd-boot.enable = true;
-      efi.canTouchEfiVariables = true;
+    boot = {
+      # Increase this from 128.
+      # It seems containerization solutions use this a lot.
+      # Then, if exhausted, deployment of sops keys fail.
+      kernel.sysctl."fs.inotify.max_user_instances" = 256;
+
+      loader = {
+        systemd-boot.enable = true;
+        efi.canTouchEfiVariables = true;
+      };
     };
 
     services = {