Quoting Peter Steele ([email protected]): > On 12/07/2015 07:49 AM, Serge Hallyn wrote: > >Quoting Peter Steele ([email protected]): > >>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 :) > > > I'm having some trouble reproducing this behavior when I launch a > container with > > lxc-start -n containername -F -o /dev/stdout -- /sbin/init log_target=console > log_level=debug > > > I'm seeing these errors when the containers are launched as part of > my automated installation framework. The installs that are done in > this manner are hands-free and the containers, once installed, are > launched with a simple
Ok, can you change the launch command in the scripts to lxc-start -n $containername -L /tmp/$containername.cout -l trace -o /tmp/$containername.dout -- /sbin/init log_target=console log_level=debug The console output will go into the .cout file and lxc debug output into .dout. _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
