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
Thanks for your dedication to our documentation. Unfortunately, we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so I've created an internal work item to incorporate your suggestions and I've reached out to our AKS storage PM to discuss further. We are closing this issue for now, but feel free to comment here as necessary. #please-close
this issue is a regression on Windows containerd, and I have verified that the original issue has been fixed in containerd 1.6.14, mountPath: 'D:' works now, details: containerd/containerd#6589 (comment)
Containerd nodepools unable to mount PV volume as "D:"
create a nodepool with containerD:
https://docs.microsoft.com/en-us/azure/aks/windows-container-cli#add-a-windows-server-node-pool-with-containerd
Follow instructions here, where for windows the document says
"For Windows Server containers, specify a mountPath using the Windows path convention, such as 'D:'."
https://docs.microsoft.com/en-us/azure/aks/azure-files-volume#mount-file-share-as-an-inline-volume
however for windows, containerD instructions on this website says
https://docs.microsoft.com/en-us/azure/aks/windows-faq#is-kubernetes-different-on-windows-and-linux
"For example, rather than a mount point of /mnt/volume in a Linux container, specify a drive letter and location such as /K/Volume to mount as the K: drive."
Either way it wont work, because all folders will be created on C: on windows nodes not in the PV.
please advise correct procedure to implement this on windows containers using containerD, syntax .
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: