Quoting Fajar A. Nugraha (l...@fajar.net):
On Tue, Oct 1, 2013 at 4:46 AM, Serge Hallyn serge.hal...@ubuntu.comwrote:
Quoting Fajar A. Nugraha (l...@fajar.net):
Would injecting tcp rst really be necessary? In my test, doing ip link
del on the host side of the interface ALWAYS
On Tue, Oct 1, 2013 at 4:46 AM, Serge Hallyn serge.hal...@ubuntu.comwrote:
Quoting Fajar A. Nugraha (l...@fajar.net):
Would injecting tcp rst really be necessary? In my test, doing ip link
del on the host side of the interface ALWAYS succeed, no matter what the
state the guest container's
Would injecting tcp rst really be necessary? In my test, doing ip link del
on the host side of the interface ALWAYS succeed, no matter
what the state the guest container's interface is.
Serge, do you have the particular commit ids for lxc.network.script.down
support? Backporting that would
Quoting Fajar A. Nugraha (l...@fajar.net):
On Mon, Sep 30, 2013 at 11:29 PM, Serge Hallyn serge.hal...@ubuntu.comwrote:
Quoting Serge Hallyn (serge.hal...@ubuntu.com):
Quoting Jäkel, Guido (g.jae...@dnb.de):
By the other hand if I prevent inside the container by
configuration
Hi,
I want to contribute an observation while playing around with my empty plain
vanilla container template: The test cyclce is to start it, open an ssh
terminal session to it, leave it idle and regular shut down the container.
Now, if the containers eth0 is brought down by the shutdown, after
Quoting Jäkel, Guido (g.jae...@dnb.de):
Hi,
I want to contribute an observation while playing around with my empty
plain vanilla container template: The test cycle is to start it,
open an ssh terminal session to it, leave it idle and regular shut down the
container.
Now, if the containers
Quoting Jäkel, Guido (g.jae...@dnb.de):
Quoting Jäkel, Guido (g.jae...@dnb.de):
Hi,
I want to contribute an observation while playing around with my empty
plain vanilla container template: The test cycle is to start it,
open an ssh terminal session to it, leave it idle and regular shut
Quoting Fajar A. Nugraha (l...@fajar.net):
On Fri, Sep 13, 2013 at 10:16 PM, Fajar A. Nugraha l...@fajar.net wrote:
On Fri, Sep 13, 2013 at 7:43 PM, Serge Hallyn
serge.hal...@ubuntu.comwrote:
I'm wondering
whether it could just be that there is a socket waiting for a tcp
On Fri, Sep 13, 2013 at 10:16 PM, Fajar A. Nugraha l...@fajar.net wrote:
On Fri, Sep 13, 2013 at 7:43 PM, Serge Hallyn serge.hal...@ubuntu.comwrote:
I'm wondering
whether it could just be that there is a socket waiting for a tcp
timeout, holding the veth open.
It may be the case.
Hello Fajar,
What I'm doing as a workaround is to wait 10 seconds after a
lxc-shutdown has completed. This alleviates the problem as by that time
it seems the network interfaces get almost always deleted. Nevertheless
sometimes they don't and the following lxc-start won't work. I found so
far,
Quoting Fajar A. Nugraha (l...@fajar.net):
On Thu, Sep 12, 2013 at 9:46 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Quoting Fajar A. Nugraha (l...@fajar.net):
Any ideas how to troubleshoot this? Is this something related to kernel
version?
If the container fails to start at all,
On Fri, Sep 13, 2013 at 7:43 PM, Serge Hallyn serge.hal...@ubuntu.comwrote:
Quoting Fajar A. Nugraha (l...@fajar.net):
On Thu, Sep 12, 2013 at 9:46 PM, Serge Hallyn serge.hal...@ubuntu.com
wrote:
Quoting Fajar A. Nugraha (l...@fajar.net):
Any ideas how to troubleshoot this? Is this
Quoting Fajar A. Nugraha (l...@fajar.net):
Any ideas how to troubleshoot this? Is this something related to kernel
version?
If the container fails to start at all, then lxc will manually delete
the veth. However if we get as far as lxc passing one end of the
veth tunnel into the container,
On Thu, Sep 12, 2013 at 9:46 PM, Serge Hallyn serge.hal...@ubuntu.com wrote:
Quoting Fajar A. Nugraha (l...@fajar.net):
Any ideas how to troubleshoot this? Is this something related to kernel
version?
If the container fails to start at all, then lxc will manually delete
the veth.
The case
14 matches
Mail list logo
