Bug#867554: rkt: fails to start containers with systemd 233

New upstream version wes released to fix the problem with systemd 234: v1.28.1 This is a minor bugfix release. It does not contain any changes to the rkt code, but it updates dependencies and runtime versions for bugfixes: * vendor: update go-systemd to v15 (#3759). rkt stopped working when

Bug#867554: rkt: fails to start containers with systemd 233

On Wed, Jul 12, 2017 at 12:20:31PM +0200, Alban Crequy wrote: > Thanks for the bug report. rkt is supposed to work with cgroup-v2 since v1.16. Seems to be broken with systemd 234 again: https://github.com/rkt/rkt/issues/3750 A new version should be out soon... -- Valentin

Bug#867554: rkt: fails to start containers with systemd 233

Hi, Thanks for the bug report. rkt is supposed to work with cgroup-v2 since v1.16. I forwarded this bug upstream: https://github.com/rkt/rkt/issues/3741 On Fri, Jul 7, 2017 at 11:56 AM, Valentin Vidic wrote: > Package: rkt > Version: 1.21.0+dfsg-1+b1 > Severity:

Bug#867554: rkt: fails to start containers with systemd 233

Package: rkt Version: 1.21.0+dfsg-1+b1 Severity: important Dear Maintainer, It seems starting a container does now work with systemd 233 anymore: # rkt run coreos.com/etcd:v3.1.7 stage1: warning: no volume specified for mount point "data-dir", implicitly creating an "empty" volume. This volume