[FAILED] Failed to start Journal Service.
systemd-journald-audit.socket failed to listen on sockets: Operation not permitted
[FAILED] Failed to listen on Journal Audit Socket.
- The same happens with systemd-nspawn -b.
As a result, the journal isn't working at all.
With a fixed systemd package, systemd in the container should realize that it cannot listen to the audit socket (as the kernel doesn't allow that -- the audit subsystem isn't fit for namespaces right now), and "sudo journalctl" should show the journal and systemd-journald.service should be running.
Test case /www.stgraber. org/2014/ 01/17/lxc- 1-0-unprivilege d-containers/
-------------
- Under Ubuntu 15.04 (or 15.10), set up an unprivileged container as in https:/
- Boot it. You'll get a lot of errors like
[FAILED] Failed to start Journal Service. journald- audit.socket failed to listen on sockets: Operation not permitted
systemd-
[FAILED] Failed to listen on Journal Audit Socket.
- The same happens with systemd-nspawn -b.
As a result, the journal isn't working at all.
With a fixed systemd package, systemd in the container should realize that it cannot listen to the audit socket (as the kernel doesn't allow that -- the audit subsystem isn't fit for namespaces right now), and "sudo journalctl" should show the journal and systemd- journald. service should be running.