-
Notifications
You must be signed in to change notification settings - Fork 42
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
Windows Server run with --cni
got [ctr: no network config found in /etc/cni/net.d: cni plugin not initialized] error
#70
Comments
Refer: containerd/nerdctl#559 (comment) Create
and create an SYMLINKD
Same step create
run
|
The symlink setup is only needed for ctr to work, but isn't required for others like crictl or kubelet and that's why that isn't part of the runtime setup script. ctr paths have been changed in https://github.com/containerd/go-cni/pull/103/files#diff-df2b994645f533d6ced46ef610f95cfc41a3cecc099a873a9b47fadccb605b9b |
I create a new Windows Server Core 2022 VM and follow Get started: Prep Windows for containers - Windows Server - Containerd script
Run script log:
Try run without
--cni
is work and with--cni
is failing, error message: 「ctr: no network config found in /etc/cni/net.d: cni plugin not initialized」, see picture:Search solution and create a
nat
network. (Theinstall-containerd-runtime.ps1
does not set this part.)Set up the Containerd network config using the same gateway and subnet.
It will get the same error message with
--cni
.The text was updated successfully, but these errors were encountered: