Now you can use docker-compose and the docker-compose.yml file to perform the same action as in fig.
Finding containers for each service and linking them together is not an easy thing. The docker-compose file from the raw github project (inserted below for posterity) is a good start so that all apache, php, and mysql services work with the docker-compose -f docker-compose.yml up .
proxy: image: jwilder/nginx-proxy ports: ['80:80'] volumes: ['/var/run/docker.sock:/tmp/docker.sock:ro'] environment: [DEFAULT_HOST=damp.dev] database: image: 'mysql:5.7' ports: ['3306:3306'] environment: [MYSQL_ROOT_PASSWORD=password] phpmyadmin: image: corbinu/docker-phpmyadmin links: ['database:mysql'] environment: [MYSQL_USERNAME=root, MYSQL_ROOT_PASSWORD=password, VIRTUAL_HOST=phpmyadmin.damp.dev] damp: image: httpd volumes: ['~/damp/damp:/usr/local/apache2/htdocs'] environment: [VIRTUAL_HOST=damp.dev]
After you do this _ and put the entry for damp.dev 127.0.0.1 in your hosts file, everything you mount in ~ / wet / wet (from this second to the last line) will be placed in the htdocs of the docker container and processed on the channel.
dampness is just the first example I found while delving into how to copy MAMP with docker. The most important thing worth noting is that you can use docker-compose instead of fig . Compose is based directly on the code base of Fig and is backward compatible with applications of Fig.
source share