[Lxc-users] Very odd lxc behavior

[Serge Hallyn]

Quoting David Parks (davidparks21 at yahoo.com):
> Today I saw this.
> 
> I had started half the containers when I noticed the problem (not all of
> them as the output below suggests).
> 
> I stopped them all (which generated some errors, seen at the end).
> 
> After stopping them all everything went back to normal and I could start
> them all successfully without "strangeness".
> 
>  
> 
>  
> 
> root at atlas01:/var/lib/lxc# lxc-list
> 
> RUNNING
> 
> ls: cannot access testdb1: No such file or directory

Is this by chance an older version of lxc?  It sounds like
there were later attempts to start testdb1, and so
/sys/fs/cgroup/freezer/lxc/testdb1 got renamed to deadXXXXX,
then the later attempt failed, so 
/sys/fs/cgroup/freezer/lxc/testdb1 ended up not existing.

Note that that behavior no longer exists in very recent lxc.
Rather, the second attempt would use
/sys/fs/cgroup/freezer/lxc/testdb1-2, and lxc-list would
ask the container monitor for the right cgroup path,
preventing this -ENOENT.  At least that's the theory :)

-serge