[lxc-users] Stopping a container

[Alvaro Miranda Aguilera]

Hello,

The lxc-attach in this case is not needed.

Try to connect to the container, and check the time it takes using a
poweroff from inside.

If you check the other emails in the post, have been some changes on how
the containers are shutdown.

Alvaro


On Sat, Jan 18, 2014 at 2:43 AM, David Shwatrz <dshwatrz at gmail.com> wrote:

> Hi,
> Strangely,
> time lxc-attach -n fedoraCT1 poweroff
> gives:
> lxc-attach: failed to clone(0x8000): Invalid argument
> lxc-attach: Invalid argument - failed to create subprocess
>
> I get the same error also with:
> lxc-attach -n fedoraCT1 poweroff
>
>
> I made a test on another machine, which runs Ubuntu OS, and I created
> an ubuntu container on it.
> In this case, stopping the container took less than a second:
>
> time lxc-stop -n ubuntuGit
>
> real 0m0.803s
> user 0m0.003s
> sys 0m0.006s
>
>
> But when I tried another test with lxc-attach, I got the same errors:
>
> lxc-attach -n ubuntuGit poweroff
> lxc-attach: failed to clone(0x8000): Invalid argument
> lxc-attach: Invalid argument - failed to create subprocess
>
>
> time lxc-attach -n ubuntuGit poweroff
> lxc-attach: failed to clone(0x8000): Invalid argument
> lxc-attach: Invalid argument - failed to create subprocess
>
>
> Any ideas about this error message of lxc-attach ?
>
> I am working with latest git tree on both fedora and ubuntu. I build it
> in both cases with --disable-python
>
> regards,
> DavidS
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Jan 16, 2014 at 10:47 PM, Alvaro Miranda Aguilera
> <kikitux at gmail.com> wrote:
> > what's the time if you shutdown the container from inside?
> >
> > time lxc-attach -n fedoraCT1 poweroff
> >
> >
> >
> >
> > On Fri, Jan 17, 2014 at 9:31 AM, David Shwatrz <dshwatrz at gmail.com>
> wrote:
> >>
> >> Hello, lxc-users,
> >>
> >> I created a container using the fedora template with the latest git
> >> LXC tree, on Fedora 20.
> >>
> >> I use the standard configuration, with veth for networking.
> >> Starting the container is very quick and it is done by:
> >> lxc-start -n fedoraCT1
> >>
> >> Stopping the container by
> >> lxc-stop -n fedoraCT1
> >> takes more than a minute. I ran:
> >>
> >> time lxc-stop -n fedoraCT1
> >>
> >> and got:
> >> real 1m0.985s
> >> user 0m0.002s
> >> sys 0m0.004s
> >>
> >> Is this normal/expected behavior with other containers, based on
> >> different templates (like ubuntu/debian)?
> >>
> >>
> >> regards,
> >> DavidS
> >> _______________________________________________
> >> lxc-users mailing list
> >> lxc-users at lists.linuxcontainers.org
> >> http://lists.linuxcontainers.org/listinfo/lxc-users
> >
> >
> >
> > _______________________________________________
> > lxc-users mailing list
> > lxc-users at lists.linuxcontainers.org
> > http://lists.linuxcontainers.org/listinfo/lxc-users
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20140121/61e2ffd0/attachment.html>