On 8 November 2016 at 01:09, Stef Walter <s...@thewalter.net> wrote:
> Nov 08 04:04:29 unassigned-hostname docker[5826]:
> time="2016-11-08T04:04:29-05:00" level=error msg="containerd: start
> container" error="oci runtime error: could not synchronise with
> container process: no subsystem for mount"
> id=4be1274a79c35a25c0ef70a866f4d20b03e5a7bf3cf60131ae49ef0ef11bfb59
> Nov 08 04:04:29 unassigned-hostname docker[5826]:
> time="2016-11-08T04:04:29.430453214-05:00" level=error msg="Handler for
> POST
> /v1.23/containers/4be1274a79c35a25c0ef70a866f4d20b03e5a7bf3cf60131ae49ef0ef11bfb59/start
> returned error: rpc error: code = 2 desc = \"oci runtime error: could
> not synchronise with container process: no subsystem for mount\""

Ouch, looks like we're now hitting
https://github.com/opencontainers/runc/issues/1175, which doesn't
appear to have a Docker or runc workaround yet (although adding
"systemd.legacy_systemd_cgroup_controller=yes" to your system boot
parameters should do the trick for now). :(


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Reply via email to