Why on earth would you do this? Docker is such a misunderstood technology.
Code on your Chromebook, tablet, and laptop with a consistent dev environment.
If you have a Windows or Mac workstation, more easily develop for Linux.
Take advantage of large cloud servers to speed up tests, compilations, downloads, and more.
Preserve battery life when you're on the go.
All intensive computation runs on your server.
You're no longer running excess instances of Chrome.
I might actually try this and a Docker registry to get some semblance of an editor per project. In some contexts I want to run many, many extensions,but for other work I'd rather not have that bloat to contend with. Also I've been really feeling the pain of navigating a PC running Unraid (lots of bare metal VMs) and a Mac laptop, trying to do development on each. My desktop is beefy, but I need to work on the go sometimes, and at times I need to use a Windows box. Right now they all have different VSCode setups. I've been meaning to get around to setting up some scheme of making my config portable, but with different paths across Ubuntu, MacOS, and Windows that seems a bit daunting to get all of my dep paths straight, like eslint and phpcs.
Okay, enough comment writing, I'm giving this a go.
Docker just makes it convenient to deploy with a run command vs making a local server on multiple machines. I haven’t tried it yet, but being able to snapshot a running machine also seems incredibly useful.
1. I first tried to install this on my Win10 VM, which needed to have Docker installed. That was a terrible idea. I completely broke my VM as Docker tried to enable Hyper-V. Friends don't let friends attempt nested virtualization. I should have just run the container on the host instead, which it supports quite well.
2. The repo worked as the blog post described on my mac. Its quick and has been able to run some tricky extensions. I need to experiment with running some external dependancies still.
3. Docker commit worked nicely, making a layer for the changes I made. Still playing with this, but wow that could be very productive if it enabled me to roll back to a tested base environment, or share a full IDE image with somebody on my team.
Is that not supported by hyper-v? It's not common, but as long as your hardware and kernel support it, Linux/KVM work with nested virtualisation out of the box.
But if you're running win10 virtually then it's not going to be able to run hyper-v, that's a limitation of window and hyper-v and not docker.
But if you're running win10 via a vm why don't you just already have the host start a linux docker vm instead of hyper-v in hyper-v?
E.g. you can't (easily) have autocomplete in C++ on VS Code on your Mac if your project doesn't target Mac and can't build there (or doesn't have the dependencies etc).
But you can do it inside a Docker image.
That being said it's still an idea, but here's hoping it works!
You can develop all your code in a fully specified environment, which makes it much easier to reproduce and deploy models and analysis.
You can (after enabling security) move your IDE to the data. Instead of transferring data back and forth you can develop where your data is stored.
Last - and most important for me - in industries like my own (healthcare), you work with highly regulated data that has to be stored securely, where having multiple copies of data on multiple laptops can pose an unacceptably large risk.
Running containers like this within a secure environment with access to the data helps us to have an ideal development environment, while ensuring the protected data remains in a secure, single location with no unnecessary duplication.
https://blog.docker.com/2013/09/docker-can-now-run-within-do...
Repeat ad infinitum until you feel secure and ephemeral enough.