Skip to content

Commit

Permalink
NEWS: PrivateNetwork implies PrivateMounts
Browse files Browse the repository at this point in the history
This is clearly a change that can break existing units, and broke my
system in at least two different ways. For this reason this should have
been added to NEWS in #26458, specifically c2da3bf, but wasn't.
  • Loading branch information
dechamps authored and yuwata committed Aug 2, 2023
1 parent 6639ac4 commit 6b2d576
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions NEWS
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,9 @@ CHANGES WITH 254:
trailing with escape as a non comment line. For details, see:
https://github.com/systemd/systemd/issues/27975

* PrivateNetwork=yes and NetworkNamespacePath= now imply
PrivateMounts=yes unless PrivateMounts=no is explicitly specified.

* Behaviour of sandboxing options for the per-user service manager
units has changed. They now imply PrivateUsers=yes, which means user
namespaces will be implicitly enabled when a sandboxing option is
Expand Down

0 comments on commit 6b2d576

Please sign in to comment.