Preserve volume data when containers are createdĬompose preserves all volumes used by your services. A custom valueįor it can be defined with the -project-directory command line option. The default project directory is the base directory of the Compose file. You can setĬOMPOSE_PROJECT_NAME environment variable. The default project name is the basename of the project directory. Same service names, from interfering with each other on a shared host or dev host, to prevent different projects, which may use the.The project name to a unique build number on a CI server, to keep builds from interfering with each other, you can set.on a dev host, to create multiple copies of a single environment, such as when you want to run a stable copy for each feature branch of a project.You can make use of this project name in several different contexts: Multiple isolated environments on a single hostĬompose uses a project name to isolate environments from each other. Variables and moving a composition between environments.Only recreate containers that have changed.Preserve volume data when containers are created.Multiple isolated environments on a single host.The features of Compose that make it effective are: MacOS on Apple silicon, Windows, and Linux,įor more information about compatibility with the compose v1 command-line, see the docker-compose compatibility list. With other Docker command-line features, and allows it to run natively on Compose V2 also supports some of the newer additions to the specification,Ĭompose V2 has been re-written in Go, which improves integration Implementations by the Docker CLI and/or Engine, and deliver features faster to This allows us to include community proposals, experimental Making this change has enabled a number of enhancements, includingĪdding the compose command directly into the Docker CLI, being able to “up” aĬompose application on cloud platforms by simply switching the Docker context,Īnd launching of Amazon ECS and Microsoft ACI.Īs the Compose specification evolves, new features land faster in the Docker CLI.Ĭompose V2 relies directly on the compose-go bindings which are maintained as part Makes a clean distinction between the Compose YAML file model and the docker-compose Introduction of the Compose specification Refer to the Installing Compose section for detailed instructions. Set up Compose V2 to act as a drop-in replacement of the previous docker-compose. If you rely on using Docker Compose as docker-compose (with a hyphen), you can Run Compose V2 by replacing the hyphen ( -) with a space, using docker compose, To support most of the previous docker-compose features and flags. The new Compose V2, which supports the compose command as part of the DockerĬompose V2 integrates compose functions into the Docker platform, continuing Stream the log output of running servicesĬompose V2 and the new docker compose command.:/code - logvolume01:/var/log depends_on : - redis redis : image : redis volumes : logvolume01 : įor more information about the Compose file, see theĬompose has commands for managing the whole lifecycle of your application: Version : " 3.9" # optional since v1.27.0 services : web : build. You can alternatively run docker-compose up using Compose standalone( docker-compose binary). Run docker compose up and the Docker compose command starts and runs your entire app. So they can be run together in an isolated environment. Using Compose is basically a three-step process:ĭefine your app’s environment with a Dockerfile so it can be reproducedĭefine the services that make up your app in docker-compose.yml You can learn more about each case in Common Use To learn more about all the features of Compose,Ĭompose works in all environments: production, staging, development, testing, as Then, with a single command, you create and start all the servicesįrom your configuration. With Compose, you use a YAML file to configure your application’s services. Looking for Compose file reference? Find the latest version here.Ĭompose is a tool for defining and running multi-container Docker applications.
0 kommentar(er)
