-
Notifications
You must be signed in to change notification settings - Fork 68
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
Pods unable to be created on windows nodes #109
Comments
Hi @lizhuqi an you please provide more details on the issue you're finding? Such as: Is this a managed K8s (AKS, EKS)? What version of K8s? K8s node config, etc? |
Can you include a few more details such as
Thanks! |
I noticed that cluster which has the issue is still using 10.0.17763.1577. I will ask the owner to upgrade to 10.0.17763.1757 first and then add more details. |
This is also reported here microsoft/hcsshim#919.
|
Is this on AKS or some other distro or DIY K8s? |
For me, it is reproduced in both AKS and AKS-Engine. |
This issue has been open for 30 days with no updates. |
1 similar comment
This issue has been open for 30 days with no updates. |
There is a fix microsoft/hcsshim#1091 (comment). |
Hope it can be merged into AKS Windows ContainerD ASAP too.
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Chou Hu ***@***.***>
Sent: Monday, August 16, 2021 10:23:29 AM
To: microsoft/Windows-Containers ***@***.***>
Cc: Zhiwei Liu ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/Windows-Containers] Pods unable to be created on windows nodes (#109)
@zhiweiv<https://github.com/zhiweiv>, I think that the fix needs to be picked up by moby at first and then we can upgrade the moby version in AKS side.
@immuzz<https://github.com/immuzz> do you know who can speed up taking the new hccshim release with this fix in next moby version?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#109 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFH3LQPHTZH6GWJSLQOVGADT5BZCDANCNFSM43TNATIA>.
|
AKS will pick up it after the containerd 1.5.x has this fix. |
@zhiweiv FYI: this fix will be backported to 1.4.x |
The fix is in latest hcsshim release: https://github.com/microsoft/hcsshim/releases/tag/v0.8.21, the next step is moby update? Anyone can push this further? |
I dont know if this will be fixed in Moby. Have you tried this with containerd? |
@AbelHu |
@kevpar could you help to confirm whether the hcsshim issue is fixed in the latest contianerd package (v0.0.42) used by AKS? |
@AbelHu What is the difference with regular Containerd? |
In AKS, Windows containerd is still in public review so we use an internal package. |
I think that @immuzz should be able to answer more details for the difference. |
Windows Containerd on AKS is going GA per Azure/AKS#1976 (comment), any update on this? |
@zhiweiv it should be coming soon. Current plan is next month. |
This issue has been open for 30 days with no updates. |
AKS Windows Containerd has been updated to 1.5.8. |
This issue has been open for 30 days with no updates. |
1 similar comment
This issue has been open for 30 days with no updates. |
@zhiweiv with containerd now GA in AKS, can you let me know if you are still seeing this issue? Else I will mark this issue as resolved. |
You can close this issue, it doesn't occur since containerd updated to 1.5.8. |
It seems that Windows OS has some issue handling concurrent actions. Concurrent actions sometimes failed to start containers on Windows.
27m Warning FailedCreatePodSandBox pod/[POD_ONE] Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "[POD_ONE]": Error response from daemon: hcsshim::PrepareLayer - failed failed in Win32: The device is not ready. (0x15)
24m Warning FailedMount pod/[POD_ONE] Unable to attach or mount volumes: unmounted volumes=[workspace-volume default-token-xyz12], unattached volumes=[workspace-volume default-token-xyz12l]: timed out waiting for the condition
30m Normal Scheduled pod/[POD_TWO] Successfully assigned cje/[POD_TWO] to [NODE_ID]
29m Warning FailedCreatePodSandBox pod/[POD_TWO] Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod "[POD_TWO]": Error response from daemon: hcsshim::PrepareLayer - failed failed in Win32: The device is not ready. (0x15)
The text was updated successfully, but these errors were encountered: