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
Docker-Desktop 4.27.0 breaks Istio on Kubernetes #7148
Comments
Note: this is also affecting Docker Desktop for Linux. |
The culprit is the kernel configuration, which disables a bunch of conntrack features required to run istio and other service meshes: -CONFIG_NF_CONNTRACK_ZONES=y
-CONFIG_NF_CONNTRACK_PROCFS=y
-CONFIG_NF_CONNTRACK_EVENTS=y
-CONFIG_NF_CONNTRACK_TIMEOUT=y
-CONFIG_NF_CONNTRACK_TIMESTAMP=y
+# CONFIG_NF_CONNTRACK_ZONES is not set
+# CONFIG_NF_CONNTRACK_PROCFS is not set
+# CONFIG_NF_CONNTRACK_EVENTS is not set
+# CONFIG_NF_CONNTRACK_TIMEOUT is not set
+# CONFIG_NF_CONNTRACK_TIMESTAMP is not set For the record, the full diff can be found here: https://gist.github.com/xvzf/7a81f881033cab9a930f081929c3c5f0 |
Thanks a lot @xvzf for fine the root cause. I'll add them back and add a few tests specific to istio. |
@xvzf do you know if only those 5 are required? How can I quickly test Istio nowadays? I haven't tried in a long time. |
Hi @dgageot, thanks for looking into this! There's a platform prerequisites section in the Istio documentation but no specific configuration options for the modules (e.g. zone support on conntrack). As for testing this specific bug, it should be sufficient to:
Also a suggestion form my colleague @jordiclariana:
works on 4.61.1 but fails on 4.27.0. Might be worth adding it to your test-suite |
Hi @xvzf! Docker Desktop 4.27.1 is out. Could you tell me if it solves your issue? |
@xvzf Sorry for the false information. I just learnt that those patches will ship with 4.27.2 |
David is back at Docker - hooray! |
Indeed :-) Have you tried to start Istio with Docker Desktop 4.27.2, Craig? |
No, I just chanced into this link in the Istio slack.
I happen to have upgraded to 4.27.1 today but I had to do it manually - as
the release notes suggested.
|
@dgageot , we did try 4.27.2 with Istio and so far so good. Seems that the problem is solved there. Thanks! |
\o/ Thanks @jordiclariana. I'm closing the issue then |
Description
After the upgrade to 4.27.0 Istio running on-top of Docker Desktop Kubernetes stops working on the
istio-init
fails to start.Here are the logs of one of the failing init containers:
Reproduce
Expected behavior
Istio works fine like in all previous releases
docker version
Client: Cloud integration: v1.0.35+desktop.10 Version: 25.0.1 API version: 1.44 Go version: go1.21.6 Git commit: 29cf629 Built: Tue Jan 23 23:06:12 2024 OS/Arch: darwin/arm64 Context: desktop-linux Server: Docker Desktop 4.27.0 (135262) Engine: Version: 25.0.1 API version: 1.44 (minimum version 1.24) Go version: go1.21.6 Git commit: 71fa3ab Built: Tue Jan 23 23:09:35 2024 OS/Arch: linux/arm64 Experimental: false containerd: Version: 1.6.27 GitCommit: a1496014c916f9e62104b33d1bb5bd03b0858e59 runc: Version: 1.1.11 GitCommit: v1.1.11-0-g4bccb38 docker-init: Version: 0.19.0 GitCommit: de40ad0
docker info
Diagnostics ID
89814F6E-F5C8-4F6E-BCA8-FE138807A3C4/20240129091521
Additional Info
No response
The text was updated successfully, but these errors were encountered: