[lxc-users] container's network behavior when host loses connectivity
jjs - mainphrame
jjs at mainphrame.com
Sun Mar 26 02:28:34 UTC 2017
I don't know if this is your problem, but I was having a similar issue,
with openvz containers. Whenever there was a momentary connectivity glitch
on the host, the containers would lose connectivity. The culprit turned out
to be Network-Manager. I removed Network-Manager and there has not been a
single container outage since then. Take it for what it's worth.
Jake
On Sat, Mar 25, 2017 at 7:20 PM, Spike <spike at drba.org> wrote:
> Hi,
>
> per subject, can somebody please chime in with the expected behavior of a
> container's network when the host loses connectivity?
>
> I've had something rather strange happening where a container lost its ip
> and claimed the dhcp was not offering one (the container is bridged onto
> the lan with a remote dhcp server).
>
> Stopping and starting the network had no effect, I had to completely
> restart the container and then its network came back. The only thing that
> had happened is that the lan/host had an outage losing its own link, but
> I'd expect the container to be able to recover from that, no? Otherwise the
> container had been working just fine for weeks.
>
> thanks,
>
> Spike
>
> _______________________________________________
> 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/20170325/9de09147/attachment.html>
More information about the lxc-users
mailing list