[Bug 1656024] Re: hostnamectl does not work inside lxd

[Stéphane Graber]

Looks like the problem is to do with systemd and it failing to spawn
units that have:

PrivateNetwork=yes

I'm not sure exactly what systemd attempts to do which doesn't work in
an unprivileged container, but the answer is almost certainly to have it
not do that :)

Re-assigning bug to systemd.

** Package changed: lxd (Ubuntu) => systemd (Ubuntu)

** Summary changed:

- hostnamectl does not work inside lxd
+ Units using PrivateNetwork=yes don't work inside user namespaces

-- 
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:
  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