> banging my head against LXC for a bit today. My latest problem is that > if a container fails to start, I run into this situation: > > # lxc-start -n node0 > lxc-start: Device or resource busy - failed to remove previous cgroup > '/sys/fs/cgroup/systemd/node0' > lxc-start: failed to spawn 'node0' > lxc-start: Device or resource busy - failed to remove cgroup > '/sys/fs/cgroup/systemd/node0'
Upon further investigation, this happens not just on failure -- I run into this situation anytime I stop a container using, e.g., lxc-stop. On the other hand, I do *not* experience this issue if I stop a container by running "halt" from inside the container. These containers are (at the moment) running a minimal Arch Linux install; a running container looks like this: # ps -e PID TTY TIME CMD 1 ? 00:00:00 systemd 14 ? 00:00:00 systemd-journal 18 ? 00:00:00 dbus-daemon 19 ? 00:00:00 systemd-logind 22 ? 00:00:00 login 23 console 00:00:00 agetty 25 tty1 00:00:00 bash 32 tty1 00:00:00 ps -- Lars Kellogg-Stedman <l...@oddbit.com> ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
