On Tue, Mar 24, 2015 at 5:52 AM, Norberto Bensa <[email protected]> wrote: > Hello, > > from time to tome, I think once per day, my containers get stuck. I found > that `service lxcfs restart` restores functionality. > > Is this a know bug? > > ii liblxc1 1.1.0-0ubuntu1 > amd64 Linux Containers userspace tools (library) > ii lxc 1.1.0-0ubuntu1 > amd64 Linux Containers userspace tools > ii lxc-templates 1.1.0-0ubuntu1 > amd64 Linux Containers userspace tools (templates) > ii lxcfs 0.6-0ubuntu2 > amd64 FUSE based filesystem for LXC > ii python3-lxc 1.1.0-0ubuntu1 > amd64 Linux Containers userspace tools (Python 3.x bindings)
I had some problems with simple test of several cycles start-stop a vivid container. Similar to your experience, restarting lxcfs solves the problem. Serge suggested running lxcfs under gdb and try to find out what's wrong when the problem occur. I haven't had time to do so though, since debugging with gdb can be somewhat complicated. If you're just a "normal" non-developer user, and using it for "production" use, then my best advice for now is "stop lxcfs, don't use any systemd-based containers". upstart/sysvinit-based containers will work even without lxcfs. If you're a developer, then compiling lxcfs with debugging info, and poking around with gdb when the problem occurs might help. -- Fajar _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
