You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After starting an isolated Hyper-V container on Windows 11 22H2+, the container does not have a vNIC attached and/or networking does not function at all.
This is easy to reproduce in a virtualized environment 100% of the time.
Does not reproduce with non-isolated containers.
To Reproduce
Set up a vanilla Windows install with Containers and Hyper-V features enabled
Download/extract containerd into C:\containerd
Download/extract windows-cni into C:\containerd\cni\bin
Thank you for creating an Issue. Please note that GitHub is not an official channel for Microsoft support requests. To create an official support request, please open a ticket here. Microsoft and the GitHub Community strive to provide a best effort in answering questions and supporting Issues on GitHub.
Describe the bug
After starting an isolated Hyper-V container on Windows 11 22H2+, the container does not have a vNIC attached and/or networking does not function at all.
This is easy to reproduce in a virtualized environment 100% of the time.
Does not reproduce with non-isolated containers.
To Reproduce
C:\containerd
C:\containerd\cni\bin
New-Item -ItemType SymbolicLink -Path "C:\Program Files\containerd\" -Target "C:\containerd\"
./ctr run --cni --isolated -t --rm mcr.microsoft.com/windows:ltsc2019-amd64 test
)ipconfig
in container is blank / networking does not workExpected behavior
Container to start with a vNIC attached and communicating with the network normally.
Configuration:
Windows 11 22H2 22621.4317
,Windows vNext 27774.rs_prerelease.250111-1221
,Windows Server 2022 20348.3091
mcr.microsoft.com/windows:ltsc2019-amd64
windows-cni 0.3.1
(release)containerd 2.0.1
(release)Configuration files
C:\containerd\config.toml
C:\containerd\cni\conf\0-containerd-nat.conf
Additional context / logs
wincni.log
hcsdiag list all
Get-HnsEndpoint | ? ID -like ""
The text was updated successfully, but these errors were encountered: