From f8e1a7a66e248c758bb3741858ccf9838f06d735 Mon Sep 17 00:00:00 2001 From: Lucas Werkmeister Date: Sun, 4 Jan 2026 14:19:14 +0100 Subject: [PATCH] man/systemd.socket: Document JoinsNamespaceOf= support MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This has been supported since systemd v242 (specifically commit 7619cb32f0 if I’m not mistaken; added to NEWS in commit 4107452e51), but the man page still claimed otherwise. --- man/systemd.socket.xml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/man/systemd.socket.xml b/man/systemd.socket.xml index 213ceffcdb..0de281f02e 100644 --- a/man/systemd.socket.xml +++ b/man/systemd.socket.xml @@ -90,7 +90,7 @@ socket passing (i.e. sockets passed in via standard input and output, using StandardInput=socket in the service file). - All network sockets allocated through .socket units are allocated in the host's network + By default, network sockets allocated through .socket units are allocated in the host's network namespace (see network_namespaces7). This does not mean however that the service activated by a configured socket unit has to be part of the host's network @@ -101,6 +101,11 @@ the host's network namespace is only permitted through the activation sockets passed in while all sockets allocated from the service code itself will be associated with the service's own namespace, and thus possibly subject to a restrictive configuration. + + Alternatively, it is possible to run a .socket unit in another network namespace + by setting in combination with JoinsNamespaceOf=, see + systemd.exec5 and + systemd.unit5 for details.