On Do, 16.11.17 10:31, Karlin High ([email protected]) wrote: > Windows Subsystem for Linux is one of my favorite Windows 10 features. > But when I am trying to set up a special Linux environment with lots > of compiled-from-source programs and dependencies, I'd rather not > clutter it all up for everything else I want to do. The systemd-nspawn > containers seem like a good solution. But when I try to use it, I get > this error: > > failed to determine whether the unified cgroups hierarchy is used: no > medium found > > I've looked around a little for solutions, but failed to find > anything. I understand this could be a Microsoft problem, not a > systemd problem. But before I go to Microsoft, I'd like to have info > like "systemd-nspawn needs X in order to work. Can we have that added > or changed?" And if the systemd development community does not have > the capacity or interest to pursue this issue; I understand - just say > so. If that's not the case, here's what I'm looking at.
nspawn needs cgroups. does windows provide cgroups? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel
