FS#51745 - [systemd] Docker needs leagacy cgroup v1

Attached to Project: Arch Linux
Opened by Xaver (x-f) - Tuesday, 08 November 2016, 13:46 GMT
Last edited by Dave Reisner (falconindy) - Sunday, 13 November 2016, 20:13 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Docker needs cgroup v1 and 232 provides cgroup v2

Bug Reports (including a workaround):
https://github.com/opencontainers/runc/issues/1175
https://github.com/docker/docker/issues/28109
This task depends upon

Closed by  Dave Reisner (falconindy)
Sunday, 13 November 2016, 20:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  systemd-232-3
Comment by Dave Reisner (falconindy) - Tuesday, 08 November 2016, 13:56 GMT
Perhaps you have systemd.unified_cgroup_hierarchy on your kernel commandline. systemd still uses cgroup v1 by default.

edit: Nope, nevermind. This isn't something for Arch to deal with, though.
Comment by Xaver (x-f) - Tuesday, 08 November 2016, 16:40 GMT
Ok, close it.
I didn't change anything on systemd related to cgroup.
It won't work with 232 and and error is identical to linked reports. (One comment was from another arch user.)
Comment by Leonid Isaev (lisaev) - Saturday, 12 November 2016, 07:27 GMT
Please note that this issue has been fixed upstream (see links in https://bugs.archlinux.org/task/51799). And why is it low priority? Currently the only way to use containers is to stick with core/systemd...
Comment by Gustavo Alvarez (sl1pkn07) - Sunday, 13 November 2016, 19:07 GMT
patch from debian

https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=77ac3825ac09d062310d50bc01bfcb0e232b8355

or upstream

https://github.com/systemd/systemd/pull/4628

Loading...