3 ms·
Some updates for those who are interested: 1. I first tried to install this on my Win10 VM, which needed to have Docker installed. That was a terrible idea. I
by reilly3000 8y ago
Some updates for those who are interested:
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.
- binalpatel 8y agoGlad it worked for you! Hadn't even thought about Docker commit, but the latter was one of the ideas I had in mind for this (not just share code with teammates, but also a fully working environment, IDE included, that they can jump right into).
- viraptor 8y ago> I completely broke my VM as Docker tried to enable Hyper-V. Friends don't let friends attempt nested virtualization. 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.
- dalore 8y agoDocker for windows uses hyper-v for it's virtualization. It works. 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?