From 72e220d998723d448164efda8e7741041a5c9fd6 Mon Sep 17 00:00:00 2001
From: Erik Arvstedt <erik.arvstedt@gmail.com>
Date: Mon, 22 Dec 2025 16:27:10 +0100
Subject: [PATCH] containers: use native systemd FUSE support

Since version 257 (NixOS 25.05), systemd-nspawn automatically creates a
/dev/fuse node in the container when the host's FUSE node is accessible
to the nspawn process:
https://github.com/systemd/systemd/pull/34067
---
 test/lib/make-test.nix | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/test/lib/make-test.nix b/test/lib/make-test.nix
index 16e2192..e710227 100644
--- a/test/lib/make-test.nix
+++ b/test/lib/make-test.nix
@@ -68,15 +68,11 @@ let
 
             # Enable FUSE inside the container when clightning replication
             # is enabled.
-            # TODO-EXTERNAL: Remove this when
-            # https://github.com/systemd/systemd/issues/17607
-            # has been resolved. This will also improve security.
             (
               let
                 s = config.config.services;
               in
                 lib.mkIf (s ? clightning && s.clightning.enable && s.clightning.replication.enable) {
-                  bindMounts."/dev/fuse" = { hostPath = "/dev/fuse"; };
                   allowedDevices = [ { node = "/dev/fuse"; modifier = "rw"; } ];
                 }
             )