cgroup issue with systemd 226

[apognu]

Hi,

I'm not sure if this falls under nomad's scope, but it would appear, as referenced in moby/moby#16256, systemd version 226 introduces init.scope into their cgroup FS, and it messes up quite a bit (nomad could not run containrs on my system).

I have not read anywhere what distros nomad means to support, so I assume recent systemd-based ones are part of it.

I understand this may not be nomad's fault and will probably be fixed upstream, but maybe the workaround could be mentionned somewhere in the docs?

Adding the following option to the Docker daemon fixed it for me:

--exec-opt native.cgroupdriver=cgroupfs

Regards,

[cbednarski]

--exec-opt native.cgroupdriver=cgroupfs

Thanks! I think we can incorporate this.

I have not read anywhere what distros nomad means to support, so I assume recent systemd-based ones are part of it.

To answer the more general question, I developed the docker integration on Ubuntu 15.04 (which uses systemd) but we do not currently support interaction with systemd.

We use docker as-is so if docker supports a particular systemd feature, Nomad will support it in that limited capacity. However, our isolation mechanisms for exec do not currently support systemd, so you may have strange compatibility problems if you run both types of workloads on a systemd system.

This is an issue we're aware of and will address but we don't have an immediate timeline for this.

[dadgar]

This should be fixed now. If it is still failing we can reopen.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.