How to use multiple YAML files to execute multiple docker container services

by Devin Yang
(This article was automatically translated.)

Published - 7 years ago ( Updated - 7 years ago )

This video introduces how to use the docker-compose command to specify multiple YAML structure language configuration files to create container execution, and introduces how we simplify docker-compose by using .env in the D-Laravel environment Start command.

D-Laravel users must watch the video, docker users, in this video, you can learn how to specify multiple yaml files at the same time by command.

Please update to the latest D-Laravel v1.2.13 to ensure that all functions can be executed normally,
Query the available version of D-Laravel./console version

Reminder:
If your D-Laravel project is already in operation, it is recommended to clone another version to try it out first.
In order to avoid site efect affecting the original normal operation of the project.
E.g:

git clone https://github.com/DevinY/dlaravel.git dlaravel-test

For a detailed introduction to D-Laravel, please refer to my GitHub URL:
https://github.com/DevinY/dlaravel

Tags: docker laravel

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

laravel

Introduced by @dump, new features in Laravel 5.6.8

In the directive of Laravel 5.6, there is a new function called @dump Let's see how cool he is.

laravel,letsencrypt,haproxy

PHPENV's HAProxy environment is set up with free SSL certificate application

PHPENV has added the support of haproxy.yml. If you have an external IP and domain name, it should be quite simple to get HAProxy and certificate application through deviny/phpenv. In this article, let us see how to use HAProxy in the HAProxy environment setting in PHPENV.

docker,phpenv

Ran out of Docker IPv4 address pool problem solving

Maybe in the old version of the docker environment, when using Docker compose to start the container, you will encounter the following error: Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network This is actually this It is a symptom of running out of default-address-pools. In some environments, docker-compose will use the private network of Class B by default. The private IP of segment 172 has a range, from 172.16.0.0 to 172.31.255.255. That is to say, when we start a docker-compose Project, it will eat a private section of Class B, which is very heroic.