On 13/10/04 10:29, Stéphane Graber wrote: > On Fri, Oct 04, 2013 at 04:11:58PM +0200, Tamas Papp wrote: > > hi, > > > > Starting a container from cli by lxc-start works fine, lxc-info shows the > > right state. > > > > Using upstart: > > > > start lxc-instance NAME=archiva-test CONFIG=/tank/lxc/archiva-test/config > > > > # lxc-info -n archiva-test > > state: STOPPED > > > > Though the container gets started. > > > > As a result I cannot use lxc-stop, lxc-ls or any other tool. > > But, stop lxc-instance... works fine. > > > > > > I was able to reproduce this issue on various machines with the latest > > daily build. > > > > > > Am I alone with this issue? > > > > > > 10x > > tamas > > > Try: lxc-info -n archiva-test -P /tank/lxc > > LXC can't guess for you where you've put your containers, so it'll look > for /var/lib/lxc by default, if they're somewhere else, you need to use > -P or set the path in /etc/lxc/lxc.conf (lxcpath = /tank/lxc)
I have also seen this problem from time to time in different boxes and different versions of lxc. It's not easily reproducible and I can't remember if I reported it (maybe not since I couldn't make a 100% reproducible test case). I also use a non-standard directory, /srv/lxc in my case. Symlinking and -P made no difference. When the bug manifests the only solution I found was a complete reboot of the host. Regards, Norberto
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
