[fearenales]

I strongly recommend you to use azk [0]. It's an alternative to docker compose but instead of being a container manager, it provides the whole environment orchestration. When compared to docker compose, azk has several advantages, such as:

  - 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.

[0] http://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