I'd guess that some container process has stuck in the kernel due to a
hardware/driver/filesystem problem. Since all containers actually share
the same kernel, there's no easy way out in this case. Check if you see
any processes of a container still running and whether you can kill them.
--
With Best Regards,
Marat Khalili
On 27/09/16 11:55, John Y. wrote:
The same as lxc-stop -n testlxc
Thank you for your help.
John
2016-09-27 14:21 GMT+08:00 Marat Khalili <[email protected] <mailto:[email protected]>>:
What's with:
# lxc-stop -n testlxc -k
?
--
With Best Regards,
Marat Khalili
On 27/09/16 05:46, John Y. wrote:
I create a container with lxc 2.0.4.
lxc-stop hangs up when I want to stop it.
#lxc-stop -n testlxc
But it may already stoped, because I exited from lxc auto
automatically and lxc-attach failed.:
#lxc-attach -n testlxc
lxc-attach: attach.c: lxc_attach_to_ns: 257 No such file or
directory - failed to open '/proc/23193/ns/mnt'
lxc-attach: attach.c: lxc_attach: 948 failed to enter the namespace
And lxc-stop still hanged without any output.
Anyone know why?
Thanks,
John
_______________________________________________
lxc-users mailing list
[email protected]
<mailto:[email protected]>
http://lists.linuxcontainers.org/listinfo/lxc-users
<http://lists.linuxcontainers.org/listinfo/lxc-users>
_______________________________________________ lxc-users mailing
list [email protected]
<mailto:[email protected]>
http://lists.linuxcontainers.org/listinfo/lxc-users
<http://lists.linuxcontainers.org/listinfo/lxc-users>
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
_______________________________________________
lxc-users mailing list
[email protected]
http://lists.linuxcontainers.org/listinfo/lxc-users
