71–73 of 73 posts
This looks cool, although for the Windows install I'd have hoped that there would be an option to integrate Hyper-V with it instead of Virtualbox, seeing as Hyper-V is available on all Windows 8.1/10 pro/enterprise systems, and having multiple virtualization platforms active on a system is generally a bad idea...
There is a hyper-v driver for docker-machine. You can use it like so: docker-machine create -d hyper-v vmname
Nice one. However, VirtualBox's shared-folder support is so god-awfully slow, that here at work we all swapped out the regular boot2docker setup for boot2docker-xhyve[0] which is so much faster at nearly everything that it's not even a comparison. Now, with ailispaw's dockeroot-xhyve you can even get a VM root image that can be grown on the fly, so you never run out of space on your VM when building large Docker imag…
What should I use in place of docker compose?
- Its manifest file is more verbose and has a greater toolset [1];
- You can persist content from inside the container way better than simply mounting volumes using docker compose [2];
- Fow now, it relies on VirtualBox (usign debian2docker) but it has a built-in function [3] to sync folders into the container using rsync (significantly increasing performance for file sharing). You can still use VirtualBox Shared Folders if you want to;
- Its built-in DNS server makes you don't worry about port mapping and docker IP issues. You can access your local app running with azk by simply accessing a custom address, like: my-app.dev.azk.io.
[1] http://docs.azk.io/en/azkfilejs/README.html
[2] http://docs.azk.io/en/reference/azkfilejs/mounts.html#persis...
[3] http://docs.azk.io/en/reference/azkfilejs/mounts.html#sync