On Thu, Aug 23, 2012 at 12:16 PM, Dan Kegel <d...@kegel.com> wrote: > I had to reboot (lxc-stop wasn't enough?) and do lxc-destroy to get > rid of the ephemeral container.
^C, ps augxw | grep lxc.*temp and then lxc-stop suffice, no reboot needed. What I'm leaning towards now is: at the start of a build, use lxc-start-ephemeral -d to start the ephemeral container, then (until I figure out a better way to do things) use schroot repeatedly to execute the build's commands inside the ephemeral chroot (but not contained); then when the build is over, use lxc-stop to get rid of the ephemeral container. I know, using schroot is very wrong, but it might do just barely enough, and I don't know how to execute a series of command in an already-started ephermeral container. - Dan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
