Setting up proxycap how to#

They allow you to run containers in k8s that look to the local file system for config or (for interpreted languages) code changes. Kubernetes hostPath volumes are incredibly useful when doing development of applications destined to run in a kubernetes environment (the primary reason I want to use docker-desktop in the first place). This little gem which isn’t mentioned anywhere in the docker-desktop docs: “ Unfortunately we don’t support hostpath volumes in wsl2.“ The next issue though was a *real* downer. So I guess I have to install and maintain 2 versions of git (and the AWS CLI since our code is in AWS CodeCommit and requires an AWS MFA git credential helper to access).

I like having the ability to use git in WSL as well as directly in the IDE. Kubernetes running in Docker-Desktop’s namespace in the HyperV VMĮverything was going swimmingly until I discovered PHP storm does not yet support running git under WSL. WSL2 running (obviously) in the HyperV VM Project files (aka the code I work on) in Windows proper (for faster indexing and external change detection)

Setting up proxycap how to#

Docker-Desktop had cleverly figured how to also run on that VM so it would theoretically not be such a resource hog and have faster file access. I was excited because the version of WSL 2 that comes with that has a real linux kernel running in a cool, super integrated HyperV VM. So I decided to take the plunge and install the recently released Windows v2004. After a few hours tons of little background tasks would start using 100% of the CPU.

Well something went horribly wrong with my laptop.