From 7661b5541760e3debca5c538174d05b7e975ab99 Mon Sep 17 00:00:00 2001
From: Euan Kemp <euank@euank.com>
Date: Sun, 25 Oct 2020 23:51:02 -0700
Subject: [PATCH] k3s: add modprobe to k3s's PATH

Otherwise we get warnings like 'level=warning msg="failed to start
br_netfilter module"' in k3s's logs.

Adding modprobe to k3s's PATH fixes the warning at least. I'm not
certain if it fixes any real issue or not.
---
 pkgs/applications/networking/cluster/k3s/default.nix | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pkgs/applications/networking/cluster/k3s/default.nix b/pkgs/applications/networking/cluster/k3s/default.nix
index ca0da973f2c6..ae98fbbcc2dc 100644
--- a/pkgs/applications/networking/cluster/k3s/default.nix
+++ b/pkgs/applications/networking/cluster/k3s/default.nix
@@ -9,6 +9,7 @@
 , buildGoPackage
 , git
 , runc
+, kmod
 , libseccomp
 , pkgconfig
 , ethtool
@@ -226,6 +227,7 @@ stdenv.mkDerivation rec {
   # https://github.com/kubernetes/kubernetes/issues/26093#issuecomment-237202494
   # Note the list in that issue is stale and some aren't relevant for k3s.
   k3sRuntimeDeps = [
+    kmod
     socat
     iptables
     iproute