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
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
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
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
>
Am 08.07.2018 um 13:43 schrieb Ryutaroh Matsumoto:
> Package: systemd-container
> Version: 239-5
> Severity: normal
>
> Dear Maintainer,
>
> According to the manual page, --property=Delegate=... with systemd-nspawn
> should let the executed container to have access to "...", but it does not
>
Package: systemd-container
Version: 239-5
Severity: normal
Dear Maintainer,
According to the manual page, --property=Delegate=... with systemd-nspawn
should let the executed container to have access to "...", but it does not
work as documented with the newest Debian package (and possibly with
6 matches
Mail list logo
