Issue with Docker-isolation #2946
-
|
Hi, I have an issue that when i try to deploy the lab after destroying it i get this error: I am using ContainerLab in an Ubuntu 24.04 machine. I have the following lab: If I reboot the machine I can work with it again, but it is not practical at all. Is this a bug or am I doing something incorrectly? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
Something is flushing your ip-tables, I think.. When Docker cannot find the stage-2 chain it aborts the network creation. Instead of restarting the machine, you can restart the docker service, this should bring the chain back as well. But check You can also try |
Beta Was this translation helpful? Give feedback.
-
|
I have tried you solution but I still get the same issue. I have tried restarting docker. I add some more debug just in case it helps. I' am using nftables instead of iptables: |
Beta Was this translation helpful? Give feedback.
-
|
I have partly solved the issue. I had to enable nftables in docker as I didn't enable it before. |
Beta Was this translation helpful? Give feedback.
-
|
Also just in case it helps this is the destroy command when it works: |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I believe I understand the issue and how to fix it. Docker added support for |
Beta Was this translation helpful? Give feedback.
Hi,
I believe I understand the issue and how to fix it. Docker added support for
nftablesa few weeks ago. Many people might have installed docker using Docker-CE which is deprecated because AI recommends it (it happened to me as well...). The solution is to uninstall Docker and reinstall it usingDocker desktopoficial.