Units using PrivateNetwork=yes don't work inside user namespaces
Bug #1656024 reported by
Jeremy Bícha
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
varnish (Ubuntu) |
New
|
Undecided
|
Unassigned |
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 post a comment you must log in.
Jan 12 16:47:07 xen systemd[7897]: systemd- hostnamed. service: Failed at step NETWORK spawning /lib/systemd/ systemd- hostnamed: Permission denied hostnamed. service: Main process exited, code=exited, status=225/NETWORK hostnamed. service: Unit entered failed state. hostnamed. service: Failed with result 'exit-code'.
Jan 12 16:47:07 xen systemd[1]: systemd-
Jan 12 16:47:07 xen systemd[1]: Failed to start Hostname Service.
Jan 12 16:47:07 xen systemd[1]: systemd-
Jan 12 16:47:07 xen systemd[1]: systemd-