Created
May 24, 2018 16:03
-
-
Save drexler/d70ab957f964dbef1153d46bd853c775 to your computer and use it in GitHub Desktop.
Install Chrome under WSL
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# assumes you have ubuntu-desktop installed which includes stock libpulse | |
sudo add-apt-repository ppa:therealkenc/wsl-pulseaudio | |
sudo apt-get update && sudo apt-get upgrade | |
# Download the stable or development Chrome .deb package - dev if you want headless functionality | |
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb | |
sudo dpkg -i google-chrome-stable_current_amd64.deb | |
sudo apt -f install # probably | |
wget https://github.com/therealkenc/libudev-stub/releases/download/v0.9.0/libudev-stub-0.9.0-WSL.deb | |
sudo dpkg -i libudev-stub-0.9.0-WSL.deb # doing this **last** is important |
If it helps anyone,
instead of installing chrome exclusively for WSL (mine's WSL1), here's what worked for me with whatever was installed on Windows:
Since ~/.bashrc references .bash_aliases, use any editor. I'm using nano here:
$ nano ~/.bash_aliases
alias chrome="powershell.exe -Command start chrome"
alias firefox="powershell.exe -Command start firefox"
Without re-starting Bash, just type:
$source ~/.bashrc
Test with alias name:
$chrome
I am still happily using WSL and looking forward for WSL 2 to be completed!
Here is a couple of Chrome related links which were helpful to me:
Thank you very very much. Works perfectly
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry, I don't know about WSL1: the best thing you can do is to migrate to WSL2, it is so much better it is really not worth to stay on WSL1.