Closed mefarazahmad closed 2 weeks ago
Action required from @aritraghosh, @julia-yin, @AllenWen-at-Azure
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
Issue needing attention of @Azure/aks-leads
@mefarazahmad Please check the $env:path and powershell version and share the results of both ws2019 and ws2022 environments.
echo $PSVersionTable.PSVersion
echo $env:PATH
This issue will now be closed because it hasn't had any activity for 7 days after stale. mefarazahmad feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.
Describe the bug When using node pool OS as Windows2022 and docker image mcr.microsoft.com/dotnet/framework/sdk:4.8-windowsservercore-ltsc2022, getting "powershell is not recognized as internal or external command" but when changes to windows2019 as node pool OS and image as "mcr.microsoft.com/dotnet/framework/sdk:4.8-windowsservercore-ltsc2019" it works
To Reproduce Steps to reproduce the behavior:
az acr build --image devops/windows:v0.0.1 --registry registryName --platform windows .
Use below docker fileand then using terraform module to create windows pods using the image build from above step
Expected behavior Kubernetes pods must run without any errors.
Screenshots
Environment (please complete the following information):