mirror of
https://github.com/docker/docs.git
synced 2026-04-05 10:48:55 +07:00
evolution of compose explainer (#16521)
* evolution of compose * fix links * clarify 'History' section * code review changes
This commit is contained in:
Allie Sadler
@@ -1675,6 +1675,8 @@ manuals:
|
||||
title: Overview
|
||||
- path: /compose/features-uses/
|
||||
title: Key features and use cases
|
||||
- path: /compose/compose-v2/
|
||||
title: Evolution of Compose
|
||||
- sectiontitle: Install Docker Compose
|
||||
section:
|
||||
- path: /compose/install/
|
||||
@@ -1687,12 +1689,7 @@ manuals:
|
||||
title: Uninstall Compose
|
||||
- path: /compose/gettingstarted/
|
||||
title: Try Docker Compose
|
||||
- sectiontitle: Compose V2
|
||||
section:
|
||||
- path: /compose/compose-v2/
|
||||
title: Overview
|
||||
- path: /compose/cli-command-compatibility/
|
||||
title: Compose v2 compatibility
|
||||
|
||||
- sectiontitle: Environment variables
|
||||
section:
|
||||
- path: /compose/environment-variables/
|
||||
|
||||
@@ -1,109 +0,0 @@
|
||||
---
|
||||
description: Compose command compatibility with docker-compose
|
||||
keywords: documentation, docs, docker, compose, containers
|
||||
title: Compose command compatibility with docker-compose
|
||||
---
|
||||
|
||||
The `compose` command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`.
|
||||
|
||||
If you see any Compose functionality that is not available in the `compose` command, create an issue in the [Compose](https://github.com/docker/compose/issues){:target="_blank" rel="noopener" class="_"} GitHub repository, so we can prioritize it.
|
||||
|
||||
## Commands or flags not yet implemented
|
||||
|
||||
The following commands have not been implemented yet, and may be implemented at a later time.
|
||||
Let us know if these commands are a higher priority for your use cases.
|
||||
|
||||
`compose build --memory`: This option is not yet supported by BuildKit. The flag is currently supported, but is hidden to avoid breaking existing Compose usage. It does not have any effect.
|
||||
|
||||
## Flags that will not be implemented
|
||||
|
||||
The list below includes the flags that we are not planning to support in Compose in the Docker CLI,
|
||||
either because they are already deprecated in `docker-compose`, or because they are not relevant for Compose in the Docker CLI.
|
||||
|
||||
* `compose ps --filter KEY-VALUE` Not relevant due to its complicated usage with the `service` command and also because it is not documented properly in `docker-compose`.
|
||||
* `compose rm --all` Deprecated in docker-compose.
|
||||
* `compose scale` Deprecated in docker-compose (use `compose up --scale` instead)
|
||||
|
||||
Global flags:
|
||||
|
||||
* `--compatibility` has been resignified Docker Compose V2. This now means that in the command running V2 will behave as V1 used to do.
|
||||
* One difference is in the word separator on container names. V1 used to use `_` as separator while V2 uses `-` to keep the names more hostname friendly. So when using `--compatibility` Docker
|
||||
Compose should use `_` again. Just make sure to stick to one of them otherwise Docker Compose will not be able to recognize the container as an instance of the service.
|
||||
|
||||
## Config command
|
||||
|
||||
The config command is intended to show the configuration used by Docker Compose to run the actual project.
|
||||
As we know, at some parts of the Compose file have a short and a long format. For example, the `ports` entry.
|
||||
In the example below we can see the config command expanding the `ports` section:
|
||||
|
||||
docker-compose.yml:
|
||||
```
|
||||
services:
|
||||
web:
|
||||
image: nginx
|
||||
ports:
|
||||
- 80:80
|
||||
```
|
||||
With `$ docker compose config` the output turns into:
|
||||
```
|
||||
services:
|
||||
web:
|
||||
image: nginx
|
||||
networks:
|
||||
default: null
|
||||
ports:
|
||||
- mode: ingress
|
||||
target: 80
|
||||
published: 80
|
||||
protocol: tcp
|
||||
networks:
|
||||
default:
|
||||
name: workspace_default
|
||||
```
|
||||
|
||||
The result above is a full size configuration of what will be used by Docker Compose to run the project.
|
||||
|
||||
## New commands introduced in Compose v2
|
||||
|
||||
### Copy
|
||||
|
||||
The `cp` command is intended to copy files or folders between service containers and the local filesystem.
|
||||
This command is a bidirectional command, we can copy **from** or **to** the service containers.
|
||||
|
||||
Copy a file from a service container to the local filesystem:
|
||||
|
||||
```console
|
||||
$ docker compose cp my-service:~/path/to/myfile ~/local/path/to/copied/file
|
||||
```
|
||||
|
||||
We can also copy from the local filesystem to all the running containers of a service:
|
||||
|
||||
```console
|
||||
$ docker compose cp --all ~/local/path/to/source/file my-service:~/path/to/copied/file
|
||||
```
|
||||
|
||||
|
||||
### List
|
||||
|
||||
The ls command is intended to list the Compose projects. By default, the command only lists the running projects,
|
||||
we can use flags to display the stopped projects, to filter by conditions and change the output to `json` format for example.
|
||||
|
||||
```console
|
||||
$ docker compose ls --all --format json
|
||||
[{"Name":"dockergithubio","Status":"exited(1)","ConfigFiles":"/path/to/docs/docker-compose.yml"}]
|
||||
```
|
||||
|
||||
## Use `--project-name` with Compose commands
|
||||
|
||||
With the GA version of Compose, you can run some commands:
|
||||
- outside of directory containing the project compose file
|
||||
- or without specifying the path of the Compose with the `--file` flag
|
||||
- or without specifying the project directory with the `--project-directory` flag
|
||||
|
||||
When a compose project has been loaded once, we can just use the `-p` or `--project-name` to reference it:
|
||||
|
||||
```console
|
||||
$ docker compose -p my-loaded-project restart my-service
|
||||
```
|
||||
|
||||
This option works with the `start`, `stop`, `restart` and `down` commands.
|
||||
@@ -1,45 +1,164 @@
|
||||
---
|
||||
description: Key features and use cases of Docker Compose
|
||||
keywords: documentation, docs, docker, compose, orchestration, containers, uses, features
|
||||
title: Compose V2 Overview
|
||||
title: Evolution of Compose
|
||||
redirect_from:
|
||||
- /compose/cli-command-compatibility/
|
||||
---
|
||||
|
||||
## Compose V2 and the new `docker compose` command
|
||||
This page provides information on the history of Compose and explains the key differences between Compose V1 and Compose V2.
|
||||
|
||||
> Important
|
||||
>
|
||||
> The new Compose V2, which supports the `compose` command as part of the Docker
|
||||
> CLI, is now available.
|
||||
>
|
||||
> Compose V2 integrates compose functions into the Docker platform, continuing
|
||||
> to support most of the previous `docker-compose` features and flags. You can
|
||||
> run Compose V2 by replacing the hyphen (`-`) with a space, using `docker compose`,
|
||||
> instead of `docker-compose`.
|
||||
{: .important}
|
||||
## History
|
||||
|
||||
If you rely on using Docker Compose as `docker-compose` (with a hyphen), you can
|
||||
set up Compose V2 to act as a drop-in replacement of the previous `docker-compose`.
|
||||
Refer to the [Installing Compose](../install/index.md) section for detailed instructions.
|
||||
The first release of Compose, written in Python, happened at the end of 2014.
|
||||
Between 2014 and 2017 two other noticeable versions of Compose, which introduced new file format versions, were released:
|
||||
|
||||
## Context of Docker Compose evolution
|
||||
- [Compose 1.6.0 with file format V2](../compose-file/compose-file-v2/)
|
||||
- [Compose 1.10.0 with file format V3](../compose-file/compose-file-v3/)
|
||||
|
||||
Introduction of the [Compose specification](https://github.com/compose-spec/compose-spec){:target="_blank" rel="noopener" class="_"}
|
||||
makes a clean distinction between the Compose YAML file model and the `docker-compose`
|
||||
These three key file format versions and releases prior to v1.29.2 are collectively referred to as Compose V1.
|
||||
|
||||
In mid-2020 Compose V2 was released. It merged Compose file format V2 and V3 and was written in Go. The file format is defined by the [Compose specification](https://github.com/compose-spec/compose-spec){:target="_blank" rel="noopener" class="_"}. Compose V2 is the latest and recommended version of Compose. It provides improved integration with other Docker command-line features, and simplified installation on macOS, Windows, and Linux.
|
||||
|
||||
It makes a clean distinction between the Compose YAML file model and the `docker-compose`
|
||||
implementation. Making this change has enabled a number of enhancements, including
|
||||
adding the `compose` command directly into the Docker CLI, being able to "up" a
|
||||
Compose application on cloud platforms by simply switching the Docker context,
|
||||
and launching of [Amazon ECS](../../cloud/ecs-integration.md) and [Microsoft ACI](../../cloud/aci-integration.md).
|
||||
As the Compose specification evolves, new features land faster in the Docker CLI.
|
||||
|
||||
> **A note about version numbers**
|
||||
>
|
||||
>In addition to Compose file format versions described above, the Compose binary itself is on a release schedule, as shown in [Compose releases](https://github.com/docker/compose/releases/). File format versions do not necessarily increment with each release. For example, Compose file format V3 was first introduced in Compose release 1.10.0, and versioned gradually in subsequent releases.
|
||||
>
|
||||
>The latest Compose file format, defined by the Compose Specification, was implemented by Docker Compose 1.27.0+.
|
||||
|
||||
## Differences between Compose V1 and Compose V2
|
||||
|
||||
Compose V2 integrates compose functions into the Docker platform, continuing to support most of the previous `docker-compose` features and flags. You can run Compose V2 by replacing the hyphen (`-`) with a space, using `docker compose`, instead of `docker-compose`.
|
||||
|
||||
The `compose` command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`.
|
||||
|
||||
If you see any Compose functionality that is not available in the `compose` command, create an issue in the [Compose](https://github.com/docker/compose/issues){:target="_blank" rel="noopener" class="_"} GitHub repository, so we can prioritize it.
|
||||
|
||||
Compose V2 relies directly on the compose-go bindings which are maintained as part
|
||||
of the specification. This allows us to include community proposals, experimental
|
||||
implementations by the Docker CLI and/or Engine, and deliver features faster to
|
||||
users. Compose V2 also supports some of the newer additions to the specification,
|
||||
such as [profiles](../profiles.md) and [GPU](../gpu-support.md) devices.
|
||||
users.
|
||||
|
||||
Compose V2 has been re-written in [Go](https://go.dev), which improves integration
|
||||
with other Docker command-line features, and allows it to run natively on
|
||||
[macOS on Apple silicon](../../desktop/install/mac-install.md), Windows, and Linux,
|
||||
without dependencies such as Python.
|
||||
<ul class="nav nav-tabs">
|
||||
<li class="active"><a data-toggle="tab" data-target="#tab1">Commands not yet implemented</a></li>
|
||||
<li><a data-toggle="tab" data-target="#tab2">Flags not be implemented</a></li>
|
||||
<li><a data-toggle="tab" data-target="#tab3">New commands in Compose v2</a></li>
|
||||
</ul>
|
||||
<div class="tab-content">
|
||||
<div id="tab1" class="tab-pane fade in active" markdown="1">
|
||||
|
||||
For more information about compatibility with the compose v1 command-line, see the [docker-compose compatibility list](../cli-command-compatibility.md).
|
||||
The following commands have not been implemented yet, and may be implemented at a later time.
|
||||
Let us know if these commands are a higher priority for your use cases.
|
||||
|
||||
`compose build --memory`: This option is not yet supported by BuildKit. The flag is currently supported, but is hidden to avoid breaking existing Compose usage. It does not have any effect.
|
||||
|
||||
<hr>
|
||||
</div>
|
||||
<div id="tab2" class="tab-pane fade" markdown="1">
|
||||
|
||||
The list below includes the flags that we are not planning to support in Compose in the Docker CLI,
|
||||
either because they are already deprecated in `docker-compose`, or because they are not relevant for Compose in the Docker CLI.
|
||||
|
||||
* `compose ps --filter KEY-VALUE` Not relevant due to its complicated usage with the `service` command and also because it is not documented properly in `docker-compose`.
|
||||
* `compose rm --all` Deprecated in docker-compose.
|
||||
* `compose scale` Deprecated in docker-compose (use `compose up --scale` instead)
|
||||
|
||||
Global flags:
|
||||
|
||||
* `--compatibility` has been resignified Docker Compose V2. This now means that in the command running V2 will behave as V1 used to do.
|
||||
* One difference is in the word separator on container names. V1 used to use `_` as separator while V2 uses `-` to keep the names more hostname friendly. So when using `--compatibility` Docker
|
||||
Compose should use `_` again. Just make sure to stick to one of them otherwise Docker Compose will not be able to recognize the container as an instance of the service.
|
||||
<hr>
|
||||
</div>
|
||||
<div id="tab3" class="tab-pane fade" markdown="1">
|
||||
|
||||
#### Copy
|
||||
|
||||
The `cp` command is intended to copy files or folders between service containers and the local filesystem.
|
||||
This command is a bidirectional command, we can copy **from** or **to** the service containers.
|
||||
|
||||
Copy a file from a service container to the local filesystem:
|
||||
|
||||
```console
|
||||
$ docker compose cp my-service:~/path/to/myfile ~/local/path/to/copied/file
|
||||
```
|
||||
|
||||
We can also copy from the local filesystem to all the running containers of a service:
|
||||
|
||||
```console
|
||||
$ docker compose cp --all ~/local/path/to/source/file my-service:~/path/to/copied/file
|
||||
```
|
||||
|
||||
|
||||
#### List
|
||||
|
||||
The ls command is intended to list the Compose projects. By default, the command only lists the running projects,
|
||||
we can use flags to display the stopped projects, to filter by conditions and change the output to `json` format for example.
|
||||
|
||||
```console
|
||||
$ docker compose ls --all --format json
|
||||
[{"Name":"dockergithubio","Status":"exited(1)","ConfigFiles":"/path/to/docs/docker-compose.yml"}]
|
||||
```
|
||||
|
||||
### Use `--project-name` with Compose commands
|
||||
|
||||
With the GA version of Compose, you can run some commands:
|
||||
- outside of directory containing the project compose file
|
||||
- or without specifying the path of the Compose with the `--file` flag
|
||||
- or without specifying the project directory with the `--project-directory` flag
|
||||
|
||||
When a compose project has been loaded once, we can just use the `-p` or `--project-name` to reference it:
|
||||
|
||||
```console
|
||||
$ docker compose -p my-loaded-project restart my-service
|
||||
```
|
||||
|
||||
This option works with the `start`, `stop`, `restart` and `down` commands.
|
||||
|
||||
### Config command
|
||||
|
||||
The config command is intended to show the configuration used by Docker Compose to run the actual project after normalization and templating. The resulting output might contain superficial differences in formattting and style.
|
||||
For example, some fields in the Compose Specification support both short and a long format so the output structure might not match the input structure but is guaranteed to be semantically equivalent.
|
||||
|
||||
Similarly, comments in the source file are not preserved.
|
||||
|
||||
In the example below we can see the config command expanding the `ports` section:
|
||||
|
||||
docker-compose.yml:
|
||||
```yaml
|
||||
services:
|
||||
web:
|
||||
# default to latest but allow overriding the tag
|
||||
image: nginx:${TAG-latest}
|
||||
ports:
|
||||
- 80:80
|
||||
```
|
||||
With `$ docker compose config` the output turns into:
|
||||
```yaml
|
||||
name: docs-example
|
||||
services:
|
||||
web:
|
||||
image: nginx:stable-alpine
|
||||
networks:
|
||||
default: null
|
||||
ports:
|
||||
- mode: ingress
|
||||
target: 80
|
||||
published: "80"
|
||||
protocol: tcp
|
||||
networks:
|
||||
default:
|
||||
name: basic_default
|
||||
```
|
||||
|
||||
The result above is a full size configuration of what will be used by Docker Compose to run the project.
|
||||
<hr>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
@@ -12,7 +12,7 @@ anywhere.
|
||||
2. Define the services that make up your app in `docker-compose.yml`
|
||||
so they can be run together in an isolated environment.
|
||||
|
||||
3. Run `docker compose up` and the [Docker compose command](compose-v2/index.md#compose-v2-and-the-new-docker-compose-command) starts and runs your entire app. You can alternatively run `docker-compose up` using Compose standalone(`docker-compose` binary).
|
||||
3. Run `docker compose up` and the Docker compose command starts and runs your entire app. You can alternatively run `docker-compose up` using Compose standalone(`docker-compose` binary).
|
||||
|
||||
A `docker-compose.yml` looks like this:
|
||||
|
||||
|
||||
@@ -7,8 +7,7 @@ title: Enabling GPU access with Compose
|
||||
Compose services can define GPU device reservations if the Docker host contains such devices and the Docker Daemon is set accordingly. For this, make sure you install the [prerequisites](../config/containers/resource_constraints.md#gpu){: target="_blank" rel="noopener" class="_" } if you have not already done so.
|
||||
|
||||
The examples in the following sections focus specifically on providing service containers access to GPU devices with Docker Compose.
|
||||
You can use either `docker-compose` or `docker compose` commands.
|
||||
See also, [Compose command compatibility with docker-compose](cli-command-compatibility.md){: target="_blank" rel="noopener" class="_" }.
|
||||
You can use either `docker-compose` or `docker compose` commands. For more information, see [Evolution of Compose](compose-v2/index.md){: target="_blank" rel="noopener" class="_" }.
|
||||
|
||||
### Enabling GPU access to service containers
|
||||
|
||||
|
||||
@@ -99,7 +99,7 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments/index.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/compose-v2/index.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
@@ -119,7 +119,7 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments/index.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/compose-v2/index.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Upgrades
|
||||
|
||||
@@ -158,7 +158,7 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
||||
|
||||
**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../use-desktop/volumes.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/compose-v2/index.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
**Skip Docker Desktop updates**: All users can now skip an update when they are prompted to install individual Docker Desktop releases.
|
||||
|
||||
|
||||
@@ -103,7 +103,7 @@ This page contains release notes for Docker Desktop for Windows 3.x.
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments/index.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/compose-v2/index.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
@@ -123,7 +123,7 @@ This page contains release notes for Docker Desktop for Windows 3.x.
|
||||
|
||||
**Dev Environments Preview**: Dev Environments enable you to seamlessly collaborate with your team members without moving between Git branches to get your code onto your team members' machines. When using Dev Environments, you can share your in-progress work with your team members in just one click, and without having to deal with any merge conflicts. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments/index.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/compose-v2/index.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
### Upgrades
|
||||
|
||||
@@ -160,7 +160,7 @@ This page contains release notes for Docker Desktop for Windows 3.x.
|
||||
|
||||
**Volume Management**: Docker Desktop users can now create and delete volumes using the Docker Dashboard and also see which volumes are being used. For more information, see [Explore volumes](../use-desktop/volumes.md).
|
||||
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/cli-command-compatibility.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
**Compose V2 beta**: Docker Desktop now includes the beta version of Compose V2, which supports the `docker compose` command as part of the Docker CLI. While `docker-compose` is still supported and maintained, Compose V2 implementation relies directly on the compose-go bindings which are maintained as part of the specification. The compose command in the Docker CLI supports most of the `docker-compose` commands and flags. It is expected to be a drop-in replacement for `docker-compose`. There are a few remaining flags that have yet to be implemented, see the [docker-compose compatibility list](../../compose/compose-v2/index.md) for more information about the flags that are supported in the new compose command. If you run into any problems with Compose V2, you can easily switch back to Compose v1 by either by making changes in Docker Desktop **Experimental** Settings, or by running the command `docker-compose disable-v2`. Let us know your feedback on the new ‘compose’ command by creating an issue in the [Compose-CLI](https://github.com/docker/compose-cli/issues) GitHub repository.
|
||||
|
||||
**Skip Docker Desktop updates**: All users can now skip an update when they are prompted to install individual Docker Desktop releases.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user