SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

nspawn: align config PrivateUsersOwnership default with CLI

Browse Source 
The `systemd-nspawn` manpage says:

    The `--private-users-ownership=auto` option is implied if
    `--private-users=pick` is used.

This is true for the CLI, but not when set in a `.nspawn` file.
Assuming these defaults should be the same across both.

This default was also not updated when `managed` was added by #35685.

As a result, this is a change in behavior for users who didn't set an
explicit `PrivateUsersOwnership=` value in their `.nspawn` file.
This commit is contained in:
Cathal Mullan
2026-09-14 08:10:27 +01:00
committed by Luca Boccassi
parent d04aa853bc
commit 1f66b52452
4 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/systemd.nspawn.xml
+5 -3
View File
@@ -582,9 +582,11 @@
<term><varname>PrivateUsersOwnership=</varname></term>
<listitem><para>Configures whether the ownership of the files and directories in the container tree
shall be adjusted to the UID/GID range used, if necessary and user namespacing is enabled. This is
equivalent to the <option>--private-users-ownership=</option> command line switch. This option is
privileged (see above).</para>
shall be adjusted to the UID/GID range used, if necessary. This is equivalent to the
<option>--private-users-ownership=</option> command line switch. This option is privileged (see
above). Defaults to <literal>auto</literal> if <varname>PrivateUsers=pick</varname> or
<varname>PrivateUsers=managed</varname> is used. This option has no effect if user namespacing is
not used.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>