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 Containerd Support #1581
Comments
/sig windows |
Thanks peri, we will investigate if there're any gap between docker and containerd on Windows. |
Hi @perithompson , may I know the version of kubelet? Originally, kubelet on Windows format the "netNS" string in this style: 1) For sandbox container, the netns is "none" 2) for workload container, the netns is in the format of "container:$sandbox_container_ID". So we have a check for the existence of ":" in the netNS string to find the infra container ID if its value is not "none". But according to the configuration of the request you have pasted, the value of netns string is neither "none" or a string including prefix "container:". I think we need to confirm the change is introduced by kubelet or containerd first. |
HI @wenyingd, this was on v1.19.1, I used cluster-api to create the cluster and set the crisocket, with containerd, I've been told that a nat network must be created for any pods to start, once this is done any other plugin can be added on top |
Got it, we will double check. |
Some more information, if we create a nat network using containerd logs
kubelet logs
|
@perithompson : We do the test using Containerd as runtime and found that antrea-agent cannot work with Containerd for now. Here're problems we found in test:
|
Create an issue for containerd because we need to let containerd team help to measure the workfow changes for Windows from Docker to containerd. |
Open an issue in hcsshim repo to request for help about how to create VNIC in container. microsoft/hcsshim#911 |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days |
Describe the problem/challenge you have
With the announcement of that windows containerd support is stable in 1.20 and the deprecation of dockershim, we would like to move forward with Windows support for containerd.
Anything else you would like to add?
I have been testing this out today and I have noticed a few errors that will need to be addressed. The first is that cni plugin will not initialise, if you add the configuration it is possible to get passed this step but then we are presented with the following error message.
SigWindowsTools has a script to install containerd on windows Server 2019 or later but once this gets setup antrea does not take over the nat network.
Sub issues
Proposals
The text was updated successfully, but these errors were encountered: