[Bug 1707901] Re: systemd-journald-audit.socket attempts to start in unpriviledged LXD container, but cannot

2017-08-21 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707901 Title: systemd-journald-audit.socket attempts to start in

[Bug 1707901] Re: systemd-journald-audit.socket attempts to start in unpriviledged LXD container, but cannot

2017-08-01 Thread Dimitri John Ledkov
Ack thanks. I think upstream actually has ConditionVirtualization=!private-users now which can come in handy to do the uid_map check. ( I have just discovered this myself). W.r.t. not needed in containers at all, also makes sense. Thanks. ** Changed in: lxd (Ubuntu) Status: New =>

[Bug 1707901] Re: systemd-journald-audit.socket attempts to start in unpriviledged LXD container, but cannot

2017-08-01 Thread Stéphane Graber
You can look at /proc/self/uid_map to see if uid 0 is mapped to a non-0 uid, which would mean that you're not getting real root. Root in an unprivileged container does hold all the capabilities, but those are tied to the user namespace so they're only useful if the resource you're trying to

[Bug 1707901] Re: systemd-journald-audit.socket attempts to start in unpriviledged LXD container, but cannot

2017-08-01 Thread Dimitri John Ledkov
can e.g. systemd-detect-virt be extended to distinguish priviledged vs unpriviledged lxc? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707901 Title: systemd-journald-audit.socket attempts to