Bug#903265: systemd-container: --property=Delegate=... does not work with systemd-nspawn, Re: Bug#903265: systemd-container: --property=Delegate=... does not work with systemd-nspawn

[Ryutaroh Matsumoto]

Control: retitle -1 systemd: outputs confusing '-.slice: Failed to set cpu.max: Operation not permitted' in systemd-nspawn container
Control: reassign -1 systemd 239-5

In a systemd-nspawn container,
cpu.weight, cpu.max, io.weight, memory.low, memory.high, memory.max, pids.max
cannot be written by the container root privilege.
It is a normal situation (I misunderstood it when I originally
filed this bug report).
On the other hand, systemd 239 tries to write values to
the above files at its boot time even in a container.
When systemd 239 is booted in a systemd-nspawn container,
it outputs the following error message. But the systemd is
only complaining against a normal and expected situation.
I believe that the following messages are simply useless
and can be safely ignored if systemd is started as PID 1
in a systemd container.

-.slice: Failed to set cpu.weight: Operation not permitted
-.slice: Failed to set cpu.max: Operation not permitted
-.slice: Failed to set io.weight: Operation not permitted
-.slice: Failed to set memory.low: Operation not permitted
-.slice: Failed to set memory.high: Operation not permitted
-.slice: Failed to set memory.max: Operation not permitted
-.slice: Failed to set pids.max: Operation not permitted

Ryutaroh