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
Control: close -1 On Wed, 11 Jul 2018 09:41:55 +0900 (JST) Ryutaroh Matsumoto wrote: > Control: severity -1 minor > Control: tags -1 + upstream > > In light of > https://github.com/systemd/systemd/issues/9539#issuecomment-404008050 > I believe that this bug is of minor severity. This is tracked upstream, there are no patches nor configuration downstream, closing. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
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
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
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
Control: severity -1 minor Control: tags -1 + upstream In light of https://github.com/systemd/systemd/issues/9539#issuecomment-404008050 I believe that this bug is of minor severity. Ryutaroh
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
Control: forwarded -1 https://github.com/systemd/systemd/issues/9539 Hi Michael, Thanks for your quick response. I reported this to the upstream as above. Ryutaroh From: Michael Biebl Date: Sun, 8 Jul 2018 19:29:52 +0200 > Try with apparmor disabled (apparmor=0 on the kernel command line) and > with kernel 4.16. If it still fails, I would report it upstream.
