Azure / bicep

Bicep is a declarative language for describing and deploying Azure resources
MIT License
3.17k stars 731 forks source link

Coudn't start client Bicep in WSL2 #7395

Closed pmalarme closed 1 year ago

pmalarme commented 2 years ago

Does this occur consistently? Yes Repro steps:

  1. Open Windows Terminal
  2. Go to folder containing Bicep templates
  3. Use: code ./
  4. Error when starting VS Code

Action: bicep.activate Error type: string Error Message: Launching server using runtime /mnt/c/Users/redacted:username/AppData/Local/Programs/Microsoft VS Code/C:\Program Files\dotnet\dotnet.exe failed.

Version: 0.7.4 OS: linux OS Release: 5.10.102.1-microsoft-standard-WSL2 Product: Visual Studio Code Product Version: 1.68.1 Language: en

code --list-extensions --show-versions: bencoleman.armview@0.4.6 eamodio.gitlens@12.1.1 GitHub.copilot@1.31.6194 GitHub.vscode-pull-request-github@0.44.0 Gruntfuggly.todo-tree@0.0.215 hashicorp.terraform@2.23.0 humao.rest-client@0.25.0 ms-azure-devops.azure-pipelines@1.205.0 ms-azuretools.vscode-apimanagement@1.0.5 ms-azuretools.vscode-azureappservice@0.24.2 ms-azuretools.vscode-azurefunctions@1.7.3 ms-azuretools.vscode-azureresourcegroups@0.5.3 ms-azuretools.vscode-azurestaticwebapps@0.11.1 ms-azuretools.vscode-azurestorage@0.14.1 ms-azuretools.vscode-azureterraform@0.3.2 ms-azuretools.vscode-azurevirtualmachines@0.6.1 ms-azuretools.vscode-bicep@0.7.4 ms-azuretools.vscode-cosmosdb@0.19.1 ms-azuretools.vscode-docker@1.22.0 ms-azuretools.vscode-logicapps@1.1.7 ms-dotnettools.vscode-dotnet-runtime@1.5.0 ms-kubernetes-tools.vscode-aks-tools@1.2.0 ms-kubernetes-tools.vscode-kubernetes-tools@1.3.10 ms-toolsai.vscode-ai@0.12.0 ms-toolsai.vscode-ai-remote@0.12.0 ms-vscode.azure-account@0.10.1 ms-vscode.azurecli@0.5.0 ms-vscode.vscode-node-azure-pack@0.4.0 msazurermtools.azurerm-vscode-tools@0.15.7 Pivotal.vscode-spring-boot@1.36.0 redhat.java@1.7.0 redhat.vscode-yaml@1.8.0 usqlextpublisher.usql-vscode-ext@0.2.15 VisualStudioExptTeam.vscodeintellicode@1.2.21 VisualStudioOnlineApplicationInsights.application-insights@0.4.2 vsciot-vscode.azure-iot-edge@1.25.9 vsciot-vscode.azure-iot-toolkit@2.17.0 vscjava.vscode-java-debug@0.41.0 vscjava.vscode-java-dependency@0.19.1 vscjava.vscode-java-pack@0.23.0 vscjava.vscode-java-test@0.35.1 vscjava.vscode-maven@0.35.2 vscjava.vscode-spring-boot-dashboard@0.4.0 vscjava.vscode-spring-initializr@0.9.0

alex-frankel commented 2 years ago

We have seen this issue on the initial install/startup in a WSL2 environment. Are you also seeing it if you re-open Bicep on second run?

alex-frankel commented 1 year ago

Closing w/o meaningful response