Markus Lippert

The `cni` flag is part of the `platformRunFlags` and only available on Linux: https://github.com/containerd/containerd/blob/af1a0908d06b4f7db4a11bfc67ecc2f34baeb04b/cmd/ctr/commands/run/run_unix.go#L82-L85 but not on Windows: https://github.com/containerd/containerd/blob/af1a0908d06b4f7db4a11bfc67ecc2f34baeb04b/cmd/ctr/commands/run/run_windows.go#L33

I tried adding the `cni` flag to the `platformRunFlags` for Windows as well in https://github.com/containerd/containerd/pull/6304 to try it out. It seems that it tries to do the right thing but...

Thanks to @kevpar I made networking work via `ctr:`: ``` ./ctr.exe run --cni -rm -t mcr.microsoft.com/windows/nanoserver:1809 test cmd /c ipconfig Windows IP Configuration Ethernet adapter vEthernet (default-test_nat): Connection-specific DNS Suffix...

@kkbruce Networking support for Windows is not implemented yet in nerdctl. Currently networking only works with crictl and ctr command line tools.

The following process seems to work for us: 1. Temporary downgrade the Azure Account Extension to v0.9.11 and reload the window 2. Run "Azure: Sign Out" and afterwards "Azure: Sign...

@wwlorey I checked a few affected users, and they all had `ADAL` set as authentication library, but many other users who don't have the problem also had `ADAL` set here....

All affected and non-affected users are using the same tenant ID and general Azure.

It seems like authentication information stored by `v0.10.0` is invalid or can't be retrieved. Today I tried using another account B in another tenant and tried using Sign Out and...

Would be great if you could at least provide a way to write the legacy credentials with the old name as a workaround. The VSC Extension API versioning (`getExtension('ms-vscode.azure-account')!.exports).getApi('1.0.0')`) is...

@gaurav2721 you need to remove the NAT CNI config from C:\etc\cni\net.d\ for the pods to use the flannel config. See https://github.com/lippertmarkus/vagrant-k8s-win-hostprocess/blob/main/setup-scripts/winworker.ps1