The graphic below shows the steps we will take during the Walkthrough section of this post: Finally, the Visual Studio Code Server running inside of the WSL2 and has the AWS Toolkit for Visual Studio Code Extension installed. Starting with the developer at the top, we then head down several layers – the developer’s machine that is running Windows, Visual Studio Code that is running on the Windows instance, followed by the Linux VM (WSL2) that is also running on the Windows instance. The following diagram depicts the overall solution. We are going to use the WSL 2 because as opposed to the WSL 1, which could not run the Docker Engine directly inside of the WSL, the WSL 2 is able to run the Docker Engine, thanks to it’s implementation of a real Linux kernel inside a lightweight virtual machine (VM). This blog post will walk you through the steps required to set up VS Code to use the WSL 2 and AL2. On the developer side of the solution, VS Code combines the simplicity of a source code editor with developer-friendly features such as IntelliSense or code completion and debugging. Targeting AL2 allows a developer to gain the benefits associated with AL2 – support for the latest EC2 features as well as better performing workloads due to the tuned Linux kernel. bashrc) to see if there are any modifications to the PATH which could be causing this problem.When a developer needs to target Amazon Linux 2 (AL2) to run their code but they only have access to a Windows development environment, they can use the Windows Subsystem for Linux (WSL) and Visual Studio Code (VS Code) to accomplish that. If that still doesn't work, then check your startup scripts (e.g.profile. While it's the default setting if missing, you might try adding it and setting it to true (although that shouldn't have any effect). If so, then change it to true (or, delete it entirely) to allow WSL to add the Windows path. Edit /etc/wsl.conf under Ubuntu and look to see if there's an section, as in: Microsoft VS Code/bin directory (wherever it is installed) in the path? If not, then WSL may not be doing its default append. should work in WSL if it is working under PowerShell.Ĭheck your $PATH under Ubuntu ( echo $PATH).
By default, WSL appends the Windows path to the default path in Ubuntu during init. If it does launch in Windows, then obviously it's in the Windows path. I don't recall if there's an option during installation to add or not add it to the Windows path, but if so, it could be that it was deselected during installation. Try reinstalling it - If it's not in the path, some other associations may not be correctly installed either. under PowerShell - Does that work? If not, then VSCode isn't in the Windows path. I doubt that's your main problem, but it could help. First, try installing the Remote - WSL extension in VSCode (or the meta Remote Development extension pack, which includes the WSL work).
0 kommentar(er)
