search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.24k stars 21.4k forks source link

Windows host process default path is showing as c:\ instead of c:\hpc on AKS cluster version 1.28.5 #121361

Closed anilkumar1619 closed 2 months ago

anilkumar1619 commented 6 months ago

Hello Team,

I am trying to deploy windows host process for containers by following below document and when checked, I noticed the default exec path in the container is showing as c:\ instead of c:\hpc.

https://learn.microsoft.com/en-us/azure/aks/use-windows-hpc

This is working as expected in 1.27.x whereas it is incorrect in 1.28.5. In 1.28.x container, $env.CONTAINER_SANDBOX_MOUNT_POINT is set to c:\hpc but while connecting it is by default taking to c:\

As per below Github issues and the document it says C:\hpc is the right path.

https://github.com/Azure/AKS/issues/3885

https://github.com/kubernetes/enhancements/tree/master/keps/sig-windows/1981-windows-privileged-container-support#container-mounts

image

Below are the screenshots for reference.

Left, 1.27.9, default working folder is expected C:\C:{container-id} which is correct. Right, 1.28.5, default working folder is supposed to be C:\hpc but it turns out to be C:\ instead.

image

Kindly check and assist if this is expected or not.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

PesalaPavan commented 6 months ago

@anilkumar1619 Thanks for your feedback! We will investigate and update as appropriate.

AjayBathini-MSFT commented 5 months ago

@anilkumar1619 Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

AbelHu commented 3 months ago

Reference: https://github.com/Azure/AKS/issues/4196#issuecomment-2194048946

rayoef commented 2 months ago

Thank you for your dedication to our documentation. Unfortunately, at this time 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 we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.

please-close