-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using PrivateNetwork seems to break on systemd 253.5 #36
Comments
Yes, and I almost forgot that I had the answer somehow... |
First of all, this namespace setup has been working flawlessly for me for years, so thank you! I recently upgraded to systemd 254 and |
This line failed; I'm not sure why, maybe |
@Jamesits , thank you for having a look. It looks like that assignment comes from lines 42-45 in
but I'm not sure where the variable |
|
@Jamesits , ah, very cool. I tried a few different IP addresses in |
On the latest systemd in Debian, the
[email protected]
unit stopped working until I removed https://github.com/Jamesits/systemd-named-netns/blob/master/services/netns%40.service#L15. I suspect there's some changes to what security settings are used which are implied by PrivateNetwork.The most obvious change (and the way I spotted this) was the associated file in
/run/netns
stopped being read-only, and instead had no permissions.The text was updated successfully, but these errors were encountered: