#NPM CONFIG SET PROXY IN BASHRC HOW TO#
#NPM CONFIG SET PROXY IN BASHRC INSTALL#
#NPM CONFIG SET PROXY IN BASHRC UPDATE#
#NPM CONFIG SET PROXY IN BASHRC CODE#

The following instructions are for Ubuntu 18.04 / 20.04, but if you happen to use a different WSL distribution, you can follow Docker’s installation guide for your distro from Docker’s installation docs. We just won’t bother starting the Docker daemon.

#NPM CONFIG SET PROXY IN BASHRC INSTALL#

We still need to install Docker and Docker Compose inside of WSL because it’ll give us access to both CLI apps. Install Docker and Docker Compose within WSL

#NPM CONFIG SET PROXY IN BASHRC HOW TO#

Docker Tip #73 goes into detail on how to do this, and it even includes links to videos on how to configure the VM. You’ll want to set up your own VM to run Docker. This is only necessary if you are NOT running Docker for Windows! If you do that, goto the “Shared Drives” setting and enable it.

#NPM CONFIG SET PROXY IN BASHRC CODE#

This step isn’t necessary but I keep my code on an internal secondary HD, so I shared my “E” drive too. You may also want to share any drives you plan on having your source code reside on. In other words, it’s very safe for this data to be transmit over plain text. The traffic isn’t even leaving your dev box since the daemon is only bound to localhost, so not even other machines on your local network will be able to connect. This is going to allow your local WSL instance to connect locally to the Docker daemon running within Docker for Windows. It mentions “use with caution” because any time you make a network connection that’s not encrypted, it’s worth talking about but in this case it’s completely safe because we’re never connecting to it over a public network. In the general settings, you’ll want to expose the daemon without TLS.ĭocker for Windows has been recently renamed to Docker Desktop, so if your settings look slightly different than the screenshot, no worries. It’s very solid in terms of performance and reliability.Ĭonfigure Docker for Windows (Docker Desktop) I use this set up pretty much every day for Rails, Flask, Phoenix, Node and Webpack driven apps. The TL DR is you can’t run anything in the foreground with interactive mode, which makes it unusable for real web development.īut with the Docker CLI configured to the remote Docker for Windows host it’s really awesome! Using this method, very large Rails applications respond in ~100ms (or ~5s when having to compile 10,000+ lines of Javascript and SCSS). If you’re wondering “why not just run docker.exe and docker-compose.exe from Docker for Windows directly in WSL?”, that’s due to a bug with running Docker or Docker Compose interactively in that environment. While the Docker daemon cannot run directly on WSL, you can use the Docker CLI to connect to a remote Docker daemon running through Docker for Windows or any other VM you create (this article covers both methods).

You can even run graphical apps and it doesn’t require a VM. If you don’t, I have another article that goes over how to set up an amazing WSL based development environment within Windows. This article expects you to have WSL set up already. Just know that I’ve moved on to using WSL 2 and that none of the steps below are necessary to do with WSL 2.

I’ve decided to keep this post unmodified and fully working for WSL 1 in case you want to continue using it. I’ve recorded a video of how I have Docker Desktop along with WSL 2 working together along with other tools that I use. They even backported in support for WSL 2 in Windows versions 19.

#NPM CONFIG SET PROXY IN BASHRC UPDATE#

Use nginx -t -c $HOME/.local/etc/nginx/nginx.Update in 2020: Now that Microsoft has released the Spring 2020 Windows update we have access to WSL 2 on all editions of Windows 10 (including Home). Nginx may complain that //sdk does not exist.

Npm config set proxy in bashrc