In the meantime if you're seeing this a lot I would recommend using wsl.exe ~ in your command line in Windows Terminal to start up in your home directory in Linux, or if you are on the latest Insider builds you can use wsl.exe -cd to start up in specific paths (check usage with wsl -help). On the WSL team we'll look into \\wsl$\ queries failing (and I'll reopen this issue to track that). In that version it now fails on start up if the starting-directory fails, rather than putting you in your %USERPROFILE% directory which caused inconsistent start up locations. Opening a folder inside the Windows Subsystem for Linux in VS Code is very similar to opening up a Windows folder from the command.
This behaviour has only shown up now as the 'on starting directory error' behaviour in Windows Terminal changed in version 1.8. For example, //wsl.localhost/Ubuntu-20.04/home/user1. button to select your starting directory or enter the WSL path as: //wsl.localhost/DISTRO NAME/home/USERNAME. The latter could happen when you're using \\wsl$\ in your starting-directory value as there seems to be an intermittent bug where querying \\wsl$\ paths sometimes fails. When you open Windows Terminal, it usually starts with a default starting directory path to your user account folder on your computer. If you are using the Windows Terminal Settings UI, rather than the settings.json file, to declare this path, you can use the Browse. This error can be caused by two things: An incorrectly formatted starting-directory format, or if the path that starting-directory is querying fails. commands to copy the file to the instance-user-name home directory. You're right ! My apologies for the comment above and closing this issue out early, I just had a quick call with and I can add some clarity here: pem file (for the key pair that you specified.
0 kommentar(er)
