[Bug 1656024] Re: Units using PrivateNetwork=yes don't work inside user namespaces

[Marlin Cremers]

I had the same problem using the varnishncsa service:

systemd[30274]: varnishncsa.service: Failed at step NETWORK spawning
/usr/bin/varnishncsa: Permission denied

Overriding PrivateNetwork to be false seems to work as a workoround.

** Also affects: varnish (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1656024

Title:
  Units using PrivateNetwork=yes don't work inside user namespaces

Status in systemd package in Ubuntu:
  Confirmed
Status in varnish package in Ubuntu:
  New

Bug description:
  lxd host is Ubuntu 17.04 Alpha amd64
  lxd container is ubuntu:16.10

  hostnamectl does not work inside the lxd container:

  $ hostnamectl status
  $ sudo hostnamectl set-hostname server.example.com
  Could not set property: Connection timed out

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1656024/+subscriptions