Open laneschmidt opened 4 years ago
I also have this issue. But apparently we are edge cases...
same issue...
@eprokhor The problem is development is extremely limited in WSL2. You have to put your project's files in your Linux system's home directory(the mounted filesystem no longer works(/mnt
).
I created a projects directory in my home directory: /home/mfish0005/projects
. Once your project files are in there download the WSL VSCode extension. Then cd
into your project's directory E.G. cd ~/projects/someAngularApp
and run code .
to open it in VSCode. Then you should be able to run the project. Getting the debugger to work properly is another story...
I'm having the same problem right now. Has anyone figured out any workarounds in the meantime?
Hi @JoannaFalkowska I don't think there is much of a workaround due to how WSL 2 is designed. It's fundamentally different than WSL 1 because you need to work directly inside of the virtual Linux environment. If you don't everything is extremely slow and you run into issues like this one.
In other words you need to serve your app directly from the Linux environment (/home/your-project-folder
) instead of the mounted filesystem (/mnt/c/your-project-folder
).
I ended up reverting back to WSL 1 for now because I don't see WSL fixing this anytime soon.
@mfish0005 I reinstalled WSL 2 and tried to go the virtual Linux environment only. Turns out there is \\wsl$\
which allows you to access the Linux FS from within Windows. So you dont have to use /mnt/c/
anymore. It works very good for me now. I run IntelliJ on Windows and have set it up to load the project from \\wsl$\home\zwarag\repos\angularproject\
. I also installed chrome within Windows and have VcXSrv running on Windows. It's strange but Chrome for whatever reason needs a Window to render in, even tho I start it in --headless
mode.
@zwarag Interesting. I had a similar setup going but it was so painfully slow(minimum 30 sec compile times) that it was unusable for me. Maybe they did some optimization. I should test it out and see
To make this run successfully, Please follow the procedure
Method 1: Most of the issues will be fixed and we can run ChromeHeadless if we download chromium version(debian) in wsl and install
step 1: install necessary packages
sudo apt-get update
sudo apt-get install -y curl unzip xvfb libxi6 libgconf-2-4
step 2: install chromium
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install ./google-chrome-stable_current_amd64.deb
If still problem persists, please follow the method 2
method 2: To run a basic Selenium UI test on any environment we need a browser and a driver to control the browser. So we've to make Windows’s Chrome browser and the chromedriver accessible from WSL.
step 1: Link Chrome browser on Windows
sudo ln -sf '/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe' /usr/bin/google-chrome
step 2: Link chromedriver on Windows
sudo ln -s /mnt/c/Users/username/node_modules/chromedriver/lib/chromedriver/chromedriver.exe /usr/bin/chromedriver
step 3: Change CHROME_BIN (environmental variable's default value)
export CHROME_BIN='/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe'
If still problem persists, please follow the method 3
Method 3: This will help run puppetteer on Ubuntu, so let's install necessary packages:
sudo apt-get install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
thank you for the post @actionanand i appreciate it, hope it leads to some success!
i am no longer using WSL/Windows at all so i have not been following this issue anymore, my apologies.
method 2: To run a basic Selenium UI test on any environment we need a browser and a driver to control the browser. So we've to make Windows’s Chrome browser and the chromedriver accessible from WSL.
step 1: Link Chrome browser on Windows
sudo ln -sf '/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe' /usr/bin/google-chrome
step 2: Link chromedriver on Windows
sudo ln -s /mnt/c/Users/username/node_modules/chromedriver/lib/chromedriver/chromedriver.exe /usr/bin/chromedriver
step 3: Change CHROME_BIN (environmental variable's default value)
export CHROME_BIN='/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe'
If still problem persists, please follow the method 3
Method 2 worked for me, however, I had to not use /mnt
. Instead, started with /c/
and all was well. WSL 1.
@zwarag I resolved the issue by removing the $DISPLAY variable in my .zshrc file. Cypress depends on the Xserver which is why that variable was set. Now I am trying to figure out how I can make both cypress and chromeHeadless play together. I don't want to rely on additional configuration to keep karma happy.
To make this run successfully, Please follow the procedure
Method 1: Most of the issues will be fixed and we can run ChromeHeadless if we download chromium version(debian) in wsl and install
step 1: install necessary packages
sudo apt-get update
sudo apt-get install -y curl unzip xvfb libxi6 libgconf-2-4
step 2: install chromium
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install ./google-chrome-stable_current_amd64.deb
If still problem persists, please follow the method 2
method 2: To run a basic Selenium UI test on any environment we need a browser and a driver to control the browser. So we've to make Windows’s Chrome browser and the chromedriver accessible from WSL.
step 1: Link Chrome browser on Windows
sudo ln -sf '/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe' /usr/bin/google-chrome
step 2: Link chromedriver on Windows
sudo ln -s /mnt/c/Users/username/node_modules/chromedriver/lib/chromedriver/chromedriver.exe /usr/bin/chromedriver
step 3: Change CHROME_BIN (environmental variable's default value)
export CHROME_BIN='/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe'
If still problem persists, please follow the method 3
Method 3: This will help run puppetteer on Ubuntu, so let's install necessary packages:
sudo apt-get install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
Method 2 worked for me. I've just replaced path 'Program Files' to without (x86)
Method 3: This will help run puppetteer on Ubuntu, so let's install necessary packages:
sudo apt-get install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
Thanks, method 3 worked for me (WSL 2).
Method 2 Step 3 was the only required step for me. Steps 1 and 2 were not needed. I had to make one small change to the path, since my executable was in Program Files
rather than Program Files (x86)
.
To make this run successfully, Please follow the procedure Method 1: Most of the issues will be fixed and we can run ChromeHeadless if we download chromium version(debian) in wsl and install step 1: install necessary packages
sudo apt-get update
sudo apt-get install -y curl unzip xvfb libxi6 libgconf-2-4
step 2: install chromiumwget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt install ./google-chrome-stable_current_amd64.deb
If still problem persists, please follow the method 2 method 2: To run a basic Selenium UI test on any environment we need a browser and a driver to control the browser. So we've to make Windows’s Chrome browser and the chromedriver accessible from WSL. step 1: Link Chrome browser on Windowssudo ln -sf '/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe' /usr/bin/google-chrome
step 2: Link chromedriver on Windowssudo ln -s /mnt/c/Users/username/node_modules/chromedriver/lib/chromedriver/chromedriver.exe /usr/bin/chromedriver
step 3: Change CHROME_BIN (environmental variable's default value)export CHROME_BIN='/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe'
If still problem persists, please follow the method 3 Method 3: This will help run puppetteer on Ubuntu, so let's install necessary packages:sudo apt-get install gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates fonts-liberation libappindicator1 libnss3 lsb-release xdg-utils wget
My StackOverflow solution linkMethod 2 worked for me. I've just replaced path 'Program Files' to without (x86)
Happy that you found it working. Happy coding 🥇
Two things: 0- Update your Chrome to latest stable ver 1- make sure about your local environment variable for CHROME_BIN
I'm using Windows Subsystem for Linux (Windows 10, Ubuntu 18.04 LTS). I'll list all the other pertinent versions below.
This setup is working on my Mac machine, without the
flags
array added tokarma.conf.ts
as shown below.So far I've looked at: Headless Chrome slows tests by 10x, rebuilding yarn project using
npm rebuild --update-binary
, #175, #198Expected Behaviour To launch ChromeHeadless and run the tests
Current Behaviour Running
yarn test
as I would normally results in this error:and after
ctrl+c
...The file
/tmp/ng-GhKvib/angular-errors.log
containsAn unhandled exception occurred: Cannot destructure property
errorof 'undefined' or 'null'.
.Karma Config
The command that
yarn test
runs isng test --karmaConfig=karma.conf.ts
.Versions
yarn=1.19.0 angular-cli=8.3.2 karma=4.1.0 karma-chrome-launcher=2.2.0 tsc=2.7.2