mirror of https://github.com/docker/docs.git
Merge pull request #22707 from aevesdocker/ADUI-1375
desktop: Dev envs update
This commit is contained in:
Allie Sadler
GitHub
parent
b8cb086852
commit
643956d16d
|
|
@ -1,52 +0,0 @@
|
|||
---
|
||||
description: Dev Environments
|
||||
keywords: Dev Environments, share, local, Compose
|
||||
title: Overview of Dev Environments
|
||||
linkTitle: Dev Environments
|
||||
weight: 130
|
||||
aliases:
|
||||
- /desktop/dev-environments/
|
||||
params:
|
||||
sidebar:
|
||||
badge:
|
||||
color: blue
|
||||
text: Beta
|
||||
---
|
||||
|
||||
{{% include "dev-envs-changing.md" %}}
|
||||
|
||||
{{< summary-bar feature_name="Dev Environments" >}}
|
||||
|
||||
Dev Environments let you create a configurable developer environment with all the code and tools you need to quickly get up and running.
|
||||
|
||||
It uses tools built into code editors that allows Docker to access code mounted into a container rather than on your local host. This isolates the tools, files and running services on your machine allowing multiple versions of them to exist side by side.
|
||||
|
||||
You can use Dev Environments through the intuitive GUI in Docker Desktop Dashboard or straight from your terminal with the new [`docker dev` CLI plugin](dev-cli.md).
|
||||
|
||||
## Use Dev Environments
|
||||
|
||||
To use Dev Environments:
|
||||
1. Navigate to the **Features in Development** tab in **Settings**.
|
||||
2. On the **Beta** tab, select **Turn on Dev Environments**.
|
||||
3. Select **Apply & restart**.
|
||||
|
||||
The Dev Environments tab is now visible in Docker Desktop Dashboard.
|
||||
|
||||
## How does it work?
|
||||
|
||||
>**Changes to Dev Environments with Docker Desktop 4.13**
|
||||
>
|
||||
>Docker has simplified how you configure your dev environment project. All you need to get started is a `compose-dev.yaml` file. If you have an existing project with a `.docker/` folder this is automatically migrated the next time you launch.
|
||||
|
||||
Dev Environments is powered by [Docker Compose](/compose/). This allows Dev Environments to take advantage of all the benefits and features of Compose whilst adding an intuitive GUI where you can launch environments with the click of a button.
|
||||
|
||||
Every dev environment you want to run needs a `compose-dev.yaml` file which configures your application's services and lives in your project directory. You don't need to be an expert in Docker Compose or write a `compose-dev.yaml` file from scratch as Dev Environments creates a starter `compose-dev.yaml` files based on the main language in your project.
|
||||
|
||||
You can also use the many [sample dev environments](https://github.com/docker/awesome-compose) as a starting point for how to integrate different services. Alternatively, see [Set up a dev environment](set-up.md) for more information.
|
||||
|
||||
## What's next?
|
||||
|
||||
Learn how to:
|
||||
- [Launch a dev environment](create-dev-env.md)
|
||||
- [Set up a dev environment](set-up.md)
|
||||
- [Distribute your dev environment](share.md)
|
||||
|
|
@ -1,132 +0,0 @@
|
|||
---
|
||||
description: Dev Environments
|
||||
keywords: Dev Environments, share, Docker Desktop, Compose, launch
|
||||
title: Launch a dev environment
|
||||
aliases:
|
||||
- /desktop/dev-environments/create-compose-dev-env/
|
||||
- /desktop/dev-environments/create-dev-env/
|
||||
weight: 10
|
||||
---
|
||||
|
||||
{{% include "dev-envs-changing.md" %}}
|
||||
|
||||
You can launch a dev environment from a:
|
||||
- Git repository
|
||||
- Branch or tag of a Git repository
|
||||
- Sub-folder of a Git repository
|
||||
- Local folder
|
||||
|
||||
This does not conflict with any of the local files or local tooling set up on your host.
|
||||
|
||||
>Tip
|
||||
>
|
||||
>Install the [Dev Environments browser extension](https://github.com/docker/dev-envs-extension) for [Chrome](https://chrome.google.com/webstore/detail/docker-dev-environments/gnagpachnalcofcblcgdbofnfakdbeka) or [Firefox](https://addons.mozilla.org/en-US/firefox/addon/docker-dev-environments/), to launch a dev environment faster.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
To get started with Dev Environments, you must also install the following tools and extension on your machine:
|
||||
|
||||
- [Git](https://git-scm.com). Make sure add Git to your PATH if you're a Windows user.
|
||||
- [Visual Studio Code](https://code.visualstudio.com/)
|
||||
- [Visual Studio Code Remote Containers Extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers)
|
||||
|
||||
After Git is installed, restart Docker Desktop. Select **Quit Docker Desktop**, and then start it again.
|
||||
|
||||
## Launch a dev environment from a Git repository
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> When cloning a Git repository using SSH, ensure you've added your SSH key to the ssh-agent. To do this, open a terminal and run `ssh-add <path to your private ssh key>`.
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> If you have enabled the WSL 2 integration in Docker Desktop for Windows, make sure you have an SSH agent running in your WSL 2 distribution.
|
||||
|
||||
{{< accordion title="How to start an SSH agent in WSL 2" >}}
|
||||
|
||||
If your WSL 2 distribution doesn't have an `ssh-agent` running, you can append this script at the end of your profile file (that is: ~/.profile, ~/.zshrc, ...).
|
||||
|
||||
```bash
|
||||
SSH_ENV="$HOME/.ssh/agent-environment"
|
||||
function start_agent {
|
||||
echo "Initializing new SSH agent..."
|
||||
/usr/bin/ssh-agent | sed 's/^echo/#echo/' > "${SSH_ENV}"
|
||||
echo succeeded
|
||||
chmod 600 "${SSH_ENV}"
|
||||
. "${SSH_ENV}" > /dev/null
|
||||
}
|
||||
# Source SSH settings, if applicable
|
||||
if [ -f "${SSH_ENV}" ]; then
|
||||
. "${SSH_ENV}" > /dev/null
|
||||
ps -ef | grep ${SSH_AGENT_PID} | grep ssh-agent$ > /dev/null || {
|
||||
start_agent;
|
||||
}
|
||||
else
|
||||
start_agent;
|
||||
fi
|
||||
```
|
||||
|
||||
{{< /accordion >}}
|
||||
|
||||
To launch a dev environment:
|
||||
|
||||
1. From the **Dev Environments** tab in Docker Dashboard, select **Create**. The **Create a Dev Environment** dialog displays.
|
||||
2. Select **Get Started**.
|
||||
3. Optional: Provide a name for you dev environment.
|
||||
4. Select **Existing Git repo** as the source and then paste your Git repository link into the field provided.
|
||||
5. Choose your IDE. You can choose either:
|
||||
- **Visual Studio Code**. The Git repository is cloned into a Volume and attaches to your containers. This allows you to develop directly inside of them using Visual Studio Code.
|
||||
- **Other**. The Git repository is cloned into your chosen local directory and attaches to your containers as a bind mount. This shares the directory from your computer to the container, and allows you to develop using any local editor or IDE.
|
||||
6. Select **Continue**.
|
||||
|
||||
To launch the application, run the command `make run` in your terminal. This opens an http server on port 8080. Open [http://localhost:8080](http://localhost:8080) in your browser to see the running application.
|
||||
|
||||
|
||||
## Launch from a specific branch or tag
|
||||
|
||||
You can launch a dev environment from a specific branch, for example a branch corresponding to a Pull Request, or a tag by adding `@mybranch` or `@tag` as a suffix to your Git URL:
|
||||
|
||||
`https://github.com/dockersamples/single-dev-env@mybranch`
|
||||
|
||||
or
|
||||
|
||||
`git@github.com:dockersamples/single-dev-env.git@mybranch`
|
||||
|
||||
Docker then clones the repository with your specified branch or tag.
|
||||
|
||||
## Launch from a subfolder of a Git repository
|
||||
|
||||
>Note
|
||||
>
|
||||
>Currently, Dev Environments is not able to detect the main language of the subdirectory. You need to define your own base image or services in a `compose-dev.yaml`file located in your subdirectory. For more information on how to configure, see the [React application with a Spring backend and a MySQL database sample](https://github.com/docker/awesome-compose/tree/master/react-java-mysql) or the [Go server with an Nginx proxy and a Postgres database sample](https://github.com/docker/awesome-compose/tree/master/nginx-golang-postgres).
|
||||
|
||||
1. From **Dev Environments** in Docker Dashboard, select **Create**. The **Create a Dev Environment** dialog displays.
|
||||
2. Select **Get Started**.
|
||||
3. Optional: Provide a name for you dev environment.
|
||||
4. Select **Existing Git repo** as the source and then paste the link of your Git repo subfolder into the field provided.
|
||||
5. Choose your IDE. You can choose either:
|
||||
- **Visual Studio Code**. The Git repository is cloned into a Volume and attaches to your containers. This allows you to develop directly inside of them using Visual Studio Code.
|
||||
- **Other**. The Git repository is cloned into your chosen local directory and attaches to your containers as a bind mount. This shares the directory from your computer to the container, and allows you to develop using any local editor or IDE.
|
||||
6. Select **Continue**.
|
||||
|
||||
To launch the application, run the command `make run` in your terminal. This opens an http server on port 8080. Open [http://localhost:8080](http://localhost:8080) in your browser to see the running application.
|
||||
|
||||
## Launch from a local folder
|
||||
|
||||
1. From **Dev Environments** in Docker Dashboard, select **Create**. The **Create a Dev Environment** dialog displays.
|
||||
2. Select **Get Started**.
|
||||
3. Optional: Provide a name for your dev environment.
|
||||
4. Choose **Local directory** as the source.
|
||||
5. Select **Select** to open the root directory of the code that you would like to work on.
|
||||
|
||||
A directory from your computer is bind mounted to the container, so any changes you make locally is reflected in the dev environment. You can use an editor or IDE of your choice.
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
> When using a local folder for a dev environment, file changes are synchronized between your environment container and your local files. This can affect the performance inside the container, depending on the number of files in your local folder and the operations performed in the container.
|
||||
|
||||
## What's next?
|
||||
|
||||
Learn how to:
|
||||
- [Set up a dev environment](set-up.md)
|
||||
- [Distribute your dev environment](share.md)
|
||||
|
|
@ -1,120 +0,0 @@
|
|||
---
|
||||
description: Set up a dev Environments
|
||||
keywords: Dev Environments, share, docker dev, Docker Desktop
|
||||
title: Use the docker dev CLI plugin
|
||||
aliases:
|
||||
- /desktop/dev-environments/dev-cli/
|
||||
---
|
||||
|
||||
{{% include "dev-envs-changing.md" %}}
|
||||
|
||||
Use the new `docker dev` CLI plugin to get the full Dev Environments experience from the terminal in addition to the Dashboard.
|
||||
|
||||
It is available with [Docker Desktop 4.13.0 and later](/manuals/desktop/release-notes.md).
|
||||
|
||||
### Usage
|
||||
|
||||
```bash
|
||||
docker dev [OPTIONS] COMMAND
|
||||
```
|
||||
|
||||
### Commands
|
||||
|
||||
| Command | Description |
|
||||
|:---------------------|:-----------------------------------------|
|
||||
| `check` | Check Dev Environments |
|
||||
| `create` | Create a new dev environment |
|
||||
| `list` | Lists all dev environments |
|
||||
| `logs` | Traces logs from a dev environment |
|
||||
| `open` | Open Dev Environment with the IDE |
|
||||
| `rm` | Removes a dev environment |
|
||||
| `start` | Starts a dev environment |
|
||||
| `stop` | Stops a dev environment |
|
||||
| `version` | Shows the Docker Dev version information |
|
||||
|
||||
### `docker dev check`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev check [OPTIONS]`
|
||||
|
||||
#### Options
|
||||
|
||||
| Name, shorthand | Description |
|
||||
|:---------------------|:------------------------------------|
|
||||
| `--format`,`-f` | Format the output. |
|
||||
|
||||
### `docker dev create`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev create [OPTIONS] REPOSITORY_URL`
|
||||
|
||||
#### Options
|
||||
|
||||
| Name, shorthand | Description |
|
||||
|:---------------------|:----------------------------------------------------------|
|
||||
| `--detach`,`-d` | Detach creates a Dev Env without attaching to it's logs. |
|
||||
| `--open`,`-o` | Open IDE after a successful creation |
|
||||
|
||||
### `docker dev list`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev list [OPTIONS]`
|
||||
|
||||
#### Options
|
||||
|
||||
| Name, shorthand | Description |
|
||||
|:---------------------|:------------------------------|
|
||||
| `--format`,`-f` | Format the output |
|
||||
| `--quiet`,`-q` | Only show dev environments names |
|
||||
|
||||
### `docker dev logs`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev logs [OPTIONS] DEV_ENV_NAME`
|
||||
|
||||
### `docker dev open`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev open DEV_ENV_NAME CONTAINER_REF [OPTIONS]`
|
||||
|
||||
#### Options
|
||||
|
||||
| Name, shorthand | Description |
|
||||
|:---------------------|:----------------------|
|
||||
| `--editor`,`-e` | Editor. |
|
||||
|
||||
### `docker dev rm`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev rm DEV_ENV_NAME`
|
||||
|
||||
### `docker dev start`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev start DEV_ENV_NAME`
|
||||
|
||||
### `docker dev stop`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev stop DEV_ENV_NAME`
|
||||
|
||||
### `docker dev version`
|
||||
|
||||
#### Usage
|
||||
|
||||
`docker dev version [OPTIONS]`
|
||||
|
||||
#### Options
|
||||
|
||||
| Name, shorthand | Description |
|
||||
|:---------------------|:----------------------------------------------|
|
||||
| `--format`,`-f` | Format the output. |
|
||||
| `--short`,`-s` | Shows only Docker Dev's version number. |
|
||||
|
|
@ -1,92 +0,0 @@
|
|||
---
|
||||
description: Set up a dev Environments
|
||||
keywords: Dev Environments, share, set up, Compose, Docker Desktop
|
||||
title: Set up a dev environment
|
||||
weight: 20
|
||||
aliases:
|
||||
- /desktop/dev-environments/set-up/
|
||||
---
|
||||
|
||||
{{% include "dev-envs-changing.md" %}}
|
||||
|
||||
>**Changes to Dev Environments with Docker Desktop 4.13**
|
||||
>
|
||||
>Docker has simplified how you configure your dev environment project. All you need to get started is a `compose-dev.yaml` file. If you have an existing project with a `.docker/` folder this is automatically migrated the next time you launch.
|
||||
>
|
||||
> If you are using `.docker/docker-compose.yaml`, we move it to `../compose-dev.yaml`.
|
||||
>If you are using `.docker/config.json`, we create a `../compose-dev.yaml` file with a single service named "app”. It is configured to use the image or Dockerfile referenced in the JSON as a starting point.
|
||||
|
||||
To set up a dev environment, there are additional configuration steps to tell Docker Desktop how to build, start, and use the right image for your services.
|
||||
|
||||
Dev Environments use a `compose-dev.yaml` file located at the root of your project. This file allows you to define the image required for a dedicated service, the ports you'd like to expose, along with additional configuration options.
|
||||
|
||||
The following is an example `compose-dev.yaml` file.
|
||||
|
||||
```yaml
|
||||
version: "3.7"
|
||||
services:
|
||||
backend:
|
||||
build:
|
||||
context: backend
|
||||
target: development
|
||||
secrets:
|
||||
- db-password
|
||||
depends_on:
|
||||
- db
|
||||
db:
|
||||
image: mariadb
|
||||
restart: always
|
||||
healthcheck:
|
||||
test: [ "CMD", "mysqladmin", "ping", "-h", "127.0.0.1", "--silent" ]
|
||||
interval: 3s
|
||||
retries: 5
|
||||
start_period: 30s
|
||||
secrets:
|
||||
- db-password
|
||||
volumes:
|
||||
- db-data:/var/lib/mysql
|
||||
environment:
|
||||
- MYSQL_DATABASE=example
|
||||
- MYSQL_ROOT_PASSWORD_FILE=/run/secrets/db-password
|
||||
expose:
|
||||
- 3306
|
||||
proxy:
|
||||
build: proxy
|
||||
ports:
|
||||
- 8080:80
|
||||
depends_on:
|
||||
- backend
|
||||
volumes:
|
||||
db-data:
|
||||
secrets:
|
||||
db-password:
|
||||
file: db/password.txt
|
||||
```
|
||||
|
||||
In the yaml file, the build context `backend` specifies that that the container should be built using the `development` stage (`target` attribute) of the Dockerfile located in the `backend` directory (`context` attribute)
|
||||
|
||||
The `development` stage of the Dockerfile is defined as follows:
|
||||
|
||||
```dockerfile
|
||||
# syntax=docker/dockerfile:1
|
||||
FROM golang:1.16-alpine AS build
|
||||
WORKDIR /go/src/github.com/org/repo
|
||||
COPY . .
|
||||
RUN go build -o server .
|
||||
FROM build AS development
|
||||
RUN apk update \
|
||||
&& apk add git
|
||||
CMD ["go", "run", "main.go"]
|
||||
FROM alpine:3.12
|
||||
EXPOSE 8000
|
||||
COPY --from=build /go/src/github.com/org/repo/server /server
|
||||
CMD ["/server"]
|
||||
```
|
||||
|
||||
The `development` target uses a `golang:1.16-alpine` image with all dependencies you need for development. You can start your project directly from VS Code and interact with the others applications or services such as the database or the frontend.
|
||||
|
||||
In the example, the Docker Compose files are the same. However, they could be different and the services defined in the main Compose file may use other targets to build or directly reference other images.
|
||||
|
||||
## What's next?
|
||||
|
||||
Learn how to [distribute your dev environment](share.md)
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
---
|
||||
description: Dev Environments
|
||||
keywords: Dev Environments, share, Docker Desktop
|
||||
title: Distribute your dev environment
|
||||
weight: 30
|
||||
aliases:
|
||||
- /desktop/dev-environments/share/
|
||||
---
|
||||
|
||||
{{% include "dev-envs-changing.md" %}}
|
||||
|
||||
The `compose-dev.yaml` config file makes distributing your dev environment easy so everyone can access the same code and any dependencies.
|
||||
|
||||
### Distribute your dev environment
|
||||
|
||||
When you are ready to share your environment, simply copy the link to the Github repo where your project is stored, and share the link with your team members.
|
||||
|
||||
You can also create a link that automatically starts your dev environment when opened. This can then be placed on a GitHub README or pasted into a Slack channel, for example.
|
||||
|
||||
To create the link simply join the following link with the link to your dev environment's GitHub repository:
|
||||
|
||||
`https://open.docker.com/dashboard/dev-envs?url=`
|
||||
|
||||
The following example opens a [Compose sample](https://github.com/docker/awesome-compose/tree/master/nginx-golang-mysql), a Go server with an Nginx proxy and a MariaDB/MySQL database, in Docker Desktop.
|
||||
|
||||
[https://open.docker.com/dashboard/dev-envs?url=https://github.com/docker/awesome-compose/tree/master/nginx-golang-mysql](https://open.docker.com/dashboard/dev-envs?url=https://github.com/docker/awesome-compose/tree/master/nginx-golang-mysql)
|
||||
|
||||
### Open a dev environment that has been distributed to you
|
||||
|
||||
To open a dev environment that has been shared with you, select the **Create** button in the top right-hand corner, select source **Existing Git repo**, and then paste the URL.
|
||||
|
|
@ -49,7 +49,7 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
|||
|
||||
### New
|
||||
|
||||
**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](/manuals/desktop/features/dev-environments/_index.md).
|
||||
**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.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -60,8 +60,8 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
|||
- Fixed network's IPAM configuration. Service can define a fixed IP. Fixes for [docker/compose-cli#1678](https://github.com/docker/compose-cli/issues/1678) and [docker/compose-cli#1816](https://github.com/docker/compose-cli/issues/1816)
|
||||
|
||||
- Dev Environments
|
||||
- Support VS Code Insiders. See [dev-environments#3](https://github.com/docker/dev-environments/issues/3)
|
||||
- Allow users to specify a branch when cloning a project. See [dev-environments#11](https://github.com/docker/dev-environments/issues/11)
|
||||
- Support VS Code Insiders.
|
||||
- Allow users to specify a branch when cloning a project.
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
|||
|
||||
### New
|
||||
|
||||
**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](/manuals/desktop/features/dev-environments/_index.md).
|
||||
**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.
|
||||
|
||||
**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](/manuals/compose/releases/migrate.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.
|
||||
|
||||
|
|
@ -90,7 +90,7 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
|||
|
||||
### New
|
||||
|
||||
**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](/manuals/desktop/features/dev-environments/_index.md).
|
||||
**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.
|
||||
|
||||
**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](/manuals/compose/releases/migrate.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.
|
||||
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ This page contains release notes for Docker Desktop for Windows 3.x.
|
|||
|
||||
### New
|
||||
|
||||
**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](/manuals/desktop/features/dev-environments/_index.md).
|
||||
**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.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -67,7 +67,7 @@ This page contains release notes for Docker Desktop for Windows 3.x.
|
|||
- Fixed network's IPAM configuration. Service can define a fixed IP. Fixes for [docker/compose-cli#1678](https://github.com/docker/compose-cli/issues/1678) and [docker/compose-cli#1816](https://github.com/docker/compose-cli/issues/1816)
|
||||
|
||||
- Dev Environments
|
||||
- Support VS Code Insiders. See [dev-environments#3](https://github.com/docker/dev-environments/issues/3)
|
||||
- Support VS Code Insiders.
|
||||
- Allow users to specify a branch when cloning a project. See [dev-environments#11](https://github.com/docker/dev-environments/issues/11)
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
|
@ -84,7 +84,7 @@ This page contains release notes for Docker Desktop for Windows 3.x.
|
|||
|
||||
### New
|
||||
|
||||
**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](/manuals/desktop/features/dev-environments/_index.md).
|
||||
**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.
|
||||
|
||||
**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](/manuals/compose/releases/migrate.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.
|
||||
|
||||
|
|
@ -98,7 +98,7 @@ This page contains release notes for Docker Desktop for Windows 3.x.
|
|||
|
||||
### New
|
||||
|
||||
**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](/manuals/desktop/features/dev-environments/_index.md).
|
||||
**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.
|
||||
|
||||
**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](/manuals/compose/releases/migrate.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.
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,6 @@ This includes:
|
|||
- [Image Access Management](/manuals/security/for-developers/access-tokens.md)
|
||||
- [Static vulnerability scanning](/manuals/docker-hub/repos/manage/vulnerability-scanning.md)
|
||||
- Viewing remote images in the Docker Dashboard
|
||||
- Setting up [Dev Environments](/manuals/desktop/features/dev-environments/_index.md)
|
||||
- Docker Build when using [BuildKit](/manuals/build/buildkit/_index.md#getting-started).
|
||||
You can work around this by disabling BuildKit. Run `DOCKER_BUILDKIT=0 docker build .` to disable BuildKit.
|
||||
- [Kubernetes](/manuals/desktop/features/kubernetes.md) (Images are download when you enable Kubernetes for the first time)
|
||||
|
|
|
|||
|
|
@ -31,7 +31,6 @@ GitHub](https://github.com/docker/for-mac/issues)
|
|||
- [Docker Desktop for Windows issues on GitHub](https://github.com/docker/for-win/issues)
|
||||
- [Docker Desktop for Linux issues on
|
||||
GitHub](https://github.com/docker/desktop-linux/issues)
|
||||
- [Dev Environments issues on GitHub](https://github.com/docker/dev-environments/issues)
|
||||
- [Docker Extensions issues on GitHub](https://github.com/docker/extensions-sdk/issues)
|
||||
|
||||
### Feedback via Community Slack channels
|
||||
|
|
@ -41,5 +40,4 @@ You can also provide feedback through the following [Docker Community Slack](htt
|
|||
- #docker-desktop-mac
|
||||
- #docker-desktop-windows
|
||||
- #docker-desktop-linux
|
||||
- #docker-dev-environments
|
||||
- #extensions
|
||||
|
|
|
|||
|
|
@ -62,6 +62,11 @@ aliases:
|
|||
- /toolbox/overview/
|
||||
- /toolbox/toolbox_install_mac/
|
||||
- /toolbox/toolbox_install_windows/
|
||||
- /desktop/features/dev-environments/
|
||||
- /desktop/features/dev-environments/create-dev-env/
|
||||
- /desktop/features/dev-environments/set-up/
|
||||
- /desktop/features/dev-environments/share/
|
||||
- /desktop/features/dev-environments/dev-cli/
|
||||
---
|
||||
|
||||
This document provides an overview of Docker features, products, and
|
||||
|
|
@ -135,8 +140,7 @@ guidance on modern equivalents.
|
|||
### Dev Environments
|
||||
|
||||
Dev Environments was a feature introduced in Docker Desktop that allowed
|
||||
developers to spin up development environments quickly. This feature is no
|
||||
longer under active development. Similar workflows can be achieved through
|
||||
developers to spin up development environments quickly. It was deprecated and removed from Docker Desktop version 4.42 and later. Similar workflows can be achieved through
|
||||
Docker Compose or by creating custom configurations tailored to specific
|
||||
project requirements.
|
||||
|
||||
|
|
|
|||
|
|
@ -73,9 +73,6 @@ For containers implicitly created by `docker build` as well as Docker
|
|||
Desktop's integrated Kubernetes, protection varies depending on the Docker
|
||||
Desktop version (see the following two FAQs).
|
||||
|
||||
ECI does not yet protect Docker Desktop Extension containers and
|
||||
[Dev Environments containers](/manuals/desktop/features/dev-environments/_index.md).
|
||||
|
||||
### Does ECI protect containers implicitly used by `docker build`?
|
||||
|
||||
Prior to Docker Desktop 4.19, ECI did not protect containers used implicitly
|
||||
|
|
|
|||
|
|
@ -83,11 +83,6 @@ arrangements are needed, just enable ECI and run the KinD tool as usual.
|
|||
Extension containers are also not yet protected by ECI. Ensure you extension
|
||||
containers come from trusted entities to avoid issues.
|
||||
|
||||
### Docker Desktop Dev Environments are not yet protected
|
||||
|
||||
Containers launched by the Docker Desktop Dev Environments feature are not yet
|
||||
protected.
|
||||
|
||||
### Docker Debug containers are not yet protected
|
||||
|
||||
[Docker Debug](https://docs.docker.com/reference/cli/docker/debug/) containers
|
||||
|
|
|
|||
|
|
@ -401,30 +401,6 @@ DockerDesktopClientV0.navigateToVolume
|
|||
|
||||
___
|
||||
|
||||
### navigateToDevEnvironments
|
||||
|
||||
▸ **navigateToDevEnvironments**(): `void`
|
||||
|
||||
Navigate to the Dev Environments window in Docker Desktop.
|
||||
|
||||
```typescript
|
||||
window.ddClient.navigateToDevEnvironments();
|
||||
```
|
||||
|
||||
> [!WARNING]
|
||||
>
|
||||
> It will be removed in a future version. Use [viewDevEnvironments](NavigationIntents.md#viewdevenvironments) instead.
|
||||
|
||||
#### Returns
|
||||
|
||||
`void`
|
||||
|
||||
#### Inherited from
|
||||
|
||||
DockerDesktopClientV0.navigateToDevEnvironments
|
||||
|
||||
___
|
||||
|
||||
## Other Methods
|
||||
|
||||
### execHostCmd
|
||||
|
|
|
|||
|
|
@ -197,24 +197,6 @@ A promise that fails if the image doesn't exist.
|
|||
|
||||
___
|
||||
|
||||
## Other Methods
|
||||
|
||||
### viewDevEnvironments
|
||||
|
||||
▸ **viewDevEnvironments**(): `Promise`<`void`\>
|
||||
|
||||
Navigate to the Dev Environments window in Docker Desktop.
|
||||
|
||||
```typescript
|
||||
ddClient.desktopUI.navigate.viewDevEnvironments()
|
||||
```
|
||||
|
||||
#### Returns
|
||||
|
||||
`Promise`<`void`\>
|
||||
|
||||
___
|
||||
|
||||
## Volume Methods
|
||||
|
||||
### viewVolumes
|
||||
|
|
|
|||
Loading…
Reference in New Issue