-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stoping/Restarting lxc containers disconnects machine from network #12482
Comments
I've been experiencing the same behavior since upgrading to Kubuntu 23.10 for I've verified that I don't experience actual network disconnectivity, just an annoying notification that I have silenced. |
@tomponline Is there any progress on this? I am still experiencing this. |
Hi @CalvoM we not yet looked at this case. I've asked @gabrielmougard to see if he can reproduce it and diagnose the issue. |
I have tried monitoring the In my case, this is very brief (I actually never noticed that before). I guess that depending on your host NIC, this delay can vary. I'll investigate this. |
@mr-cal @CalvoM @tomponline I found a hack:
...which should keep the bridge from going down when the last container is stopped. Here is my result: My flapping seems to have disappeared. Can you try that on your side to see if this is related? If yes, I'll work on a LXD fix to setup this behaviour internally. |
I think I might be having the same or at least a very similar issue on my setup. I am running a Dietpi OS setup. (For those unfamiliar, Dietpi is a minimal fork of Debian, with focus on optimisations for single board computers such as Raspberry Pi). I initially posted this issue on Dietpi's issue tracker MichaIng/DietPi#6884, but after some investigation, the issue seems to be with lxd itself rather than with Dietpi. On my system the hosts network connection is lost "permanently", until it is manually brought online with An interesting thing is that after the network interface as manually been brought up with As a workaround, I have found that modifying the The issue is not present in a fresh headless install of Debian Bookworm, even though that Debian and Dietpi seems to share the exact same network setup. That is to say that on Debian, is the issue not present even though the network interface is configured with |
@CalvoM can you reproduce this workaround ? |
Required information
Issue description
Whenever I restart or stop a container my network is interrupted and I lose connection for a second.
Steps to reproduce
Information to attach
Here is the output of
ip a
Output of 'ip -r`
Output of
lxc network show lxdbr0
Output of
lxc config show SampleJammy --expanded
dmesg
)lxc info NAME --show-log
)lxc config show NAME --expanded
)lxc monitor
while reproducing the issue)The text was updated successfully, but these errors were encountered: