Quoting Peter Steele ([email protected]): > On 12/04/2015 01:38 PM, Serge Hallyn wrote: > >My guess is that the no such file or directory is talking about a > >cgroup dir. what does /proc/1/cgroup in the container show? Make sure > >to run the latest lxcfs on the host, as that's needed because > >systemd moves itself to name=systemd:/init.scope cgroup. > > > >When systemd is having trouble, you can usually find out more info by running > > > >lxc-start -n containername -F -o /dev/stdout -- /sbin/init > >log_target=console log_level=debug > > > I'm actually not (yet) running lxcfs. My understanding was that it > isn't absolutely required but it does offer several benefits. I'd > planned to tackle lxcfs after getting things running without it > first, and my containers appear to be running reasonably okay > (although I am seeing some odd behavior). If it's *is* needed, then > I guess it's time to tackle lxcfs.
Oh right, since you're running your containers unconfined, you should be fine without it. Still would be useful to see systemd's output :) _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
