mirror of https://github.com/docker/docs.git
chore: rewrite links from index.md to _index.md
Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>
This commit is contained in:
David Karlsson
parent
19f0010442
commit
6e4790e291
|
|
@ -107,7 +107,7 @@ Docker API. The Docker client can communicate with more than one daemon.
|
|||
|
||||
### Docker Desktop
|
||||
|
||||
Docker Desktop is an easy-to-install application for your Mac, Windows or Linux environment that enables you to build and share containerized applications and microservices. Docker Desktop includes the Docker daemon (`dockerd`), the Docker client (`docker`), Docker Compose, Docker Content Trust, Kubernetes, and Credential Helper. For more information, see [Docker Desktop](/manuals/desktop/index.md).
|
||||
Docker Desktop is an easy-to-install application for your Mac, Windows or Linux environment that enables you to build and share containerized applications and microservices. Docker Desktop includes the Docker daemon (`dockerd`), the Docker client (`docker`), Docker Compose, Docker Content Trust, Kubernetes, and Credential Helper. For more information, see [Docker Desktop](/manuals/desktop/_index.md).
|
||||
|
||||
### Docker registries
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ The language-specific guides walk you through the process of:
|
|||
In addition to the language-specific modules, Docker documentation also provides guidelines to build images and efficiently manage your development environment. For more information, refer to the following topics:
|
||||
|
||||
* [Building best practices](/manuals/build/building/best-practices.md)
|
||||
* [Build images with BuildKit](/manuals/build/buildkit/index.md#getting-started)
|
||||
* [Build images with BuildKit](/manuals/build/buildkit/_index.md#getting-started)
|
||||
|
||||
## Language-specific guides
|
||||
|
||||
|
|
|
|||
|
|
@ -35,9 +35,9 @@ so *go* (pun intended) check it out!
|
|||
You also must know some basic [Docker concepts](/get-started/docker-concepts/the-basics/what-is-a-container.md) as well as to
|
||||
be at least vaguely familiar with the [Dockerfile format](/manuals/build/concepts/dockerfile.md).
|
||||
|
||||
Your Docker set-up must have BuildKit enabled. BuildKit is enabled by default for all users on [Docker Desktop](/manuals/desktop/index.md).
|
||||
Your Docker set-up must have BuildKit enabled. BuildKit is enabled by default for all users on [Docker Desktop](/manuals/desktop/_index.md).
|
||||
If you have installed Docker Desktop, you don’t have to manually enable BuildKit. If you are running Docker on Linux,
|
||||
please check out BuildKit [getting started](/manuals/build/buildkit/index.md#getting-started) page.
|
||||
please check out BuildKit [getting started](/manuals/build/buildkit/_index.md#getting-started) page.
|
||||
|
||||
Some familiarity with the command line is also expected.
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ application.
|
|||
|
||||
To complete this tutorial, you need the following:
|
||||
|
||||
- Docker running locally. Follow the [instructions to download and install Docker](/manuals/desktop/index.md).
|
||||
- Docker running locally. Follow the [instructions to download and install Docker](/manuals/desktop/_index.md).
|
||||
- An IDE or a text editor to edit files. [Visual Studio Code](https://code.visualstudio.com/) is a free and popular choice but you can use anything you feel comfortable with.
|
||||
- A Git client. This guide uses a command-line based `git` client, but you are free to use whatever works for you.
|
||||
- A command-line terminal application. The examples shown in this module are from the Linux shell, but they should work in PowerShell, Windows Command Prompt, or OS X Terminal with minimal, if any, modifications.
|
||||
|
|
@ -310,7 +310,7 @@ successfully built your image named `docker-gs-ping`.
|
|||
|
||||
To see the list of images you have on your local machine, you have two options.
|
||||
One is to use the CLI and the other is to use [Docker
|
||||
Desktop](/manuals/desktop/index.md). Since you're currently working in the
|
||||
Desktop](/manuals/desktop/_index.md). Since you're currently working in the
|
||||
terminal, take a look at listing images with the CLI.
|
||||
|
||||
To list images, run the `docker image ls`command (or the `docker images` shorthand):
|
||||
|
|
|
|||
|
|
@ -571,7 +571,7 @@ networks:
|
|||
```
|
||||
|
||||
|
||||
This Docker Compose configuration is super convenient as you don't have to type all the parameters to pass to the `docker run` command. You can declaratively do that in the Docker Compose file. The [Docker Compose documentation pages](/manuals/compose/index.md) are quite extensive and include a full reference for the Docker Compose file format.
|
||||
This Docker Compose configuration is super convenient as you don't have to type all the parameters to pass to the `docker run` command. You can declaratively do that in the Docker Compose file. The [Docker Compose documentation pages](/manuals/compose/_index.md) are quite extensive and include a full reference for the Docker Compose file format.
|
||||
|
||||
### The `.env` file
|
||||
|
||||
|
|
|
|||
|
|
@ -273,7 +273,7 @@ have these variables defined yet.
|
|||
|
||||
## Configure and run a development container
|
||||
|
||||
You can use a bind mount to mount your source code into the container. The container can then see the changes you make to the code immediately, as soon as you save a file. This means that you can run processes, like nodemon, in the container that watch for filesystem changes and respond to them. To learn more about bind mounts, see [Storage overview](/manuals/engine/storage/index.md).
|
||||
You can use a bind mount to mount your source code into the container. The container can then see the changes you make to the code immediately, as soon as you save a file. This means that you can run processes, like nodemon, in the container that watch for filesystem changes and respond to them. To learn more about bind mounts, see [Storage overview](/manuals/engine/storage/_index.md).
|
||||
|
||||
In addition to adding a bind mount, you can configure your Dockerfile and `compose.yaml` file to install development dependencies and run development tools.
|
||||
|
||||
|
|
|
|||
|
|
@ -319,7 +319,7 @@ In this section, you took a look at setting up your Compose file to run your Rus
|
|||
|
||||
Related information:
|
||||
- [Docker volumes](/manuals/engine/storage/volumes.md)
|
||||
- [Compose overview](/manuals/compose/index.md)
|
||||
- [Compose overview](/manuals/compose/_index.md)
|
||||
|
||||
## Next steps
|
||||
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@ When running Ollama in a container, you should have a CUDA-supported GPU. While
|
|||
To run Ollama in a container and provide GPU access:
|
||||
1. Install the prerequisites.
|
||||
- For Docker Engine on Linux, install the [NVIDIA Container Toolkilt](https://github.com/NVIDIA/nvidia-container-toolkit).
|
||||
- For Docker Desktop on Windows 10/11, install the latest [NVIDIA driver](https://www.nvidia.com/Download/index.aspx) and make sure you are using the [WSL2 backend](/manuals/desktop/wsl/index.md#turn-on-docker-desktop-wsl-2)
|
||||
- For Docker Desktop on Windows 10/11, install the latest [NVIDIA driver](https://www.nvidia.com/Download/index.aspx) and make sure you are using the [WSL2 backend](/manuals/desktop/wsl/_index.md#turn-on-docker-desktop-wsl-2)
|
||||
2. Add the Ollama service and a volume in your `compose.yaml`. The following is
|
||||
the updated `compose.yaml`:
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ There is no limit to the number of organizations you can have under a company la
|
|||
2. In the left navigation, select your company in the drop-down menu.
|
||||
3. Select the organization that you want to manage.
|
||||
|
||||
For more details about managing an organization, see [Organization administration](../organization/index.md).
|
||||
For more details about managing an organization, see [Organization administration](../organization/_index.md).
|
||||
{{< /tab >}}
|
||||
|
||||
{{< /tabs >}}
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ You can add organizations to a company in the [Admin Console](../../admin/compan
|
|||
|
||||
### How does a company owner manage SSO/SCIM settings from a company?
|
||||
|
||||
See your [SCIM](scim.md) and [SSO](../../security/for-admins/single-sign-on/configure/index.md) settings.
|
||||
See your [SCIM](scim.md) and [SSO](../../security/for-admins/single-sign-on/configure/_index.md) settings.
|
||||
|
||||
### How does a company owner enable group mapping in an IdP?
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ aliases:
|
|||
A Docker ID is a username for your Docker account that lets you access Docker products. All you need is an email address to create a Docker ID, or you can sign up with your Google or GitHub account. Your Docker ID must be between 4 and 30 characters long, and can only contain
|
||||
numbers and lowercase letters. You can't use any special characters or spaces.
|
||||
|
||||
For more information, see [Docker ID](/accounts/create-account/). If your administrator enforces [single sign-on (SSO)](../../security/for-admins/single-sign-on/index.md), this provisions a Docker ID for new users.
|
||||
For more information, see [Docker ID](/accounts/create-account/). If your administrator enforces [single sign-on (SSO)](../../security/for-admins/single-sign-on/_index.md), this provisions a Docker ID for new users.
|
||||
|
||||
Developers may have multiple Docker IDs in order to separate their Docker IDs associated with an organization with a Docker Business or Team subscription, and their personal use Docker IDs.
|
||||
|
||||
|
|
|
|||
|
|
@ -89,7 +89,7 @@ configure your organization.
|
|||
members in each team. See [Create a team](./manage-a-team.md) for details.
|
||||
|
||||
- **Repositories**: Displays a list of repositories associated with the
|
||||
organization. See [Repositories](../../docker-hub/repos/index.md) for detailed information about
|
||||
organization. See [Repositories](../../docker-hub/repos/_index.md) for detailed information about
|
||||
working with repositories.
|
||||
|
||||
- **Activity** Displays the audit logs, a chronological list of activities that
|
||||
|
|
|
|||
|
|
@ -70,4 +70,4 @@ selected when you invoke builds.
|
|||
- For information about how to interact with and manage builders,
|
||||
see [Manage builders](./manage.md)
|
||||
- To learn about different types of builders,
|
||||
see [Build drivers](drivers/index.md)
|
||||
see [Build drivers](drivers/_index.md)
|
||||
|
|
|
|||
|
|
@ -146,7 +146,7 @@ The legacy Docker Engine builder processes all stages of a Dockerfile leading
|
|||
up to the selected `--target`. It will build a stage even if the selected
|
||||
target doesn't depend on that stage.
|
||||
|
||||
[BuildKit](../buildkit/index.md) only builds the stages that the target stage
|
||||
[BuildKit](../buildkit/_index.md) only builds the stages that the target stage
|
||||
depends on.
|
||||
|
||||
For example, given the following Dockerfile:
|
||||
|
|
@ -163,7 +163,7 @@ FROM base AS stage2
|
|||
RUN echo "stage2"
|
||||
```
|
||||
|
||||
With [BuildKit enabled](../buildkit/index.md#getting-started), building the
|
||||
With [BuildKit enabled](../buildkit/_index.md#getting-started), building the
|
||||
`stage2` target in this Dockerfile means only `base` and `stage2` are processed.
|
||||
There is no dependency on `stage1`, so it's skipped.
|
||||
|
||||
|
|
|
|||
|
|
@ -140,7 +140,7 @@ with both parameters to find the results that work best for you.
|
|||
### Cache compression
|
||||
|
||||
The cache compression options are the same as the
|
||||
[exporter compression options](../../exporters/index.md#compression). This is
|
||||
[exporter compression options](../../exporters/_index.md#compression). This is
|
||||
supported by the `local` and `registry` cache backends.
|
||||
|
||||
For example, to compress the `registry` cache with `zstd` compression:
|
||||
|
|
@ -154,7 +154,7 @@ $ docker buildx build --push -t <registry>/<image> \
|
|||
### OCI media types
|
||||
|
||||
The cache OCI options are the same as the
|
||||
[exporter OCI options](../../exporters/index.md#oci-media-types). These are
|
||||
[exporter OCI options](../../exporters/_index.md#oci-media-types). These are
|
||||
supported by the `local` and `registry` cache backends.
|
||||
|
||||
For example, to export OCI media type cache, use the `oci-mediatypes` property:
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@ Here's a breakdown of what this Dockerfile does:
|
|||
|
||||
The first line to add to a Dockerfile is a [`# syntax` parser directive](/reference/dockerfile.md#syntax).
|
||||
While optional, this directive instructs the Docker builder what syntax to use
|
||||
when parsing the Dockerfile, and allows older Docker versions with [BuildKit enabled](../buildkit/index.md#getting-started)
|
||||
when parsing the Dockerfile, and allows older Docker versions with [BuildKit enabled](../buildkit/_index.md#getting-started)
|
||||
to use a specific [Dockerfile frontend](../buildkit/frontend.md) before
|
||||
starting the build. [Parser directives](/reference/dockerfile.md#parser-directives)
|
||||
must appear before any other comment, whitespace, or Dockerfile instruction in
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ handling `SIGTERM` properly.
|
|||
|
||||
Compose uses the project name to create unique identifiers for all of a
|
||||
project's containers and other resources. To run multiple copies of a project,
|
||||
set a custom project name using the [`-p` command line option](reference/index.md)
|
||||
set a custom project name using the [`-p` command line option](reference/_index.md)
|
||||
or the [`COMPOSE_PROJECT_NAME` environment variable](environment-variables/envvars.md#compose_project_name).
|
||||
|
||||
### Can I use JSON instead of YAML for my Compose file?
|
||||
|
|
|
|||
|
|
@ -349,6 +349,6 @@ This is a simplified example, but it demonstrates the basic principle of `includ
|
|||
## Where to go next
|
||||
|
||||
- Try the [Sample apps with Compose](https://github.com/docker/awesome-compose)
|
||||
- [Explore the full list of Compose commands](reference/index.md)
|
||||
- [Explore the Compose file reference](/reference/compose-file/index.md)
|
||||
- [Explore the full list of Compose commands](reference/_index.md)
|
||||
- [Explore the Compose file reference](/reference/compose-file/_index.md)
|
||||
- [Check out the Learning Docker Compose video on LinkedIn Learning](https://www.linkedin.com/learning/learning-docker-compose/)
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ other containers on that network, and discoverable by the service's name.
|
|||
>
|
||||
> Your app's network is given a name based on the "project name",
|
||||
> which is based on the name of the directory it lives in. You can override the
|
||||
> project name with either the [`--project-name` flag](reference/index.md)
|
||||
> project name with either the [`--project-name` flag](reference/_index.md)
|
||||
> or the [`COMPOSE_PROJECT_NAME` environment variable](environment-variables/envvars.md#compose_project_name).
|
||||
|
||||
For example, suppose your app is in a directory called `myapp`, and your `compose.yml` looks like this:
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ Once you have a second configuration file, you can use it with the
|
|||
$ docker compose -f compose.yml -f production.yml up -d
|
||||
```
|
||||
|
||||
See [Using multiple compose files](multiple-compose-files/index.md) for a more complete example, and other options.
|
||||
See [Using multiple compose files](multiple-compose-files/_index.md) for a more complete example, and other options.
|
||||
|
||||
### Deploying changes
|
||||
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ Valid profiles names follow the regex format of `[a-zA-Z0-9][a-zA-Z0-9_.-]+`.
|
|||
|
||||
## Start specific profiles
|
||||
|
||||
To start a specific profile supply the `--profile` [command-line option](reference/index.md) or
|
||||
To start a specific profile supply the `--profile` [command-line option](reference/_index.md) or
|
||||
use the [`COMPOSE_PROFILES` environment variable](environment-variables/envvars.md#compose_profiles):
|
||||
|
||||
```console
|
||||
|
|
@ -175,7 +175,7 @@ $ COMPOSE_PROFILES=dev docker compose up phpmyadmin
|
|||
|
||||
## Stop specific profiles
|
||||
|
||||
As with starting specific profiles, you can use the `--profile` [command-line option](reference/index.md) or
|
||||
As with starting specific profiles, you can use the `--profile` [command-line option](reference/_index.md) or
|
||||
use the [`COMPOSE_PROFILES` environment variable](environment-variables/envvars.md#compose_profiles):
|
||||
|
||||
```console
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ weight: 140
|
|||
---
|
||||
|
||||
The following samples show the various aspects of how to work with Docker
|
||||
Compose. As a prerequisite, be sure to [install Docker Compose](install/index.md)
|
||||
Compose. As a prerequisite, be sure to [install Docker Compose](install/_index.md)
|
||||
if you have not already done so.
|
||||
|
||||
## Key concepts these samples cover
|
||||
|
|
@ -15,12 +15,12 @@ if you have not already done so.
|
|||
The samples should help you to:
|
||||
|
||||
- Define services based on Docker images using
|
||||
[Compose files](/reference/compose-file/index.md): `compose.yml` and
|
||||
[Compose files](/reference/compose-file/_index.md): `compose.yml` and
|
||||
`docker-stack.yml`
|
||||
- Understand the relationship between `compose.yml` and
|
||||
[Dockerfiles](/reference/dockerfile/)
|
||||
- Learn how to make calls to your application services from Compose files
|
||||
- Learn how to deploy applications and services to a [swarm](/manuals/engine/swarm/index.md)
|
||||
- Learn how to deploy applications and services to a [swarm](/manuals/engine/swarm/_index.md)
|
||||
|
||||
## Samples tailored to demo Compose
|
||||
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ computer, for example.
|
|||
|
||||
> Should I back up my containers?
|
||||
>
|
||||
> If you use volumes or bind-mounts to store your container data, backing up your containers may not be needed, but make sure to remember the options that were used when creating the container or use a [Docker Compose file](/reference/compose-file/index.md) if you want to re-create your containers with the same configuration after re-installation.
|
||||
> If you use volumes or bind-mounts to store your container data, backing up your containers may not be needed, but make sure to remember the options that were used when creating the container or use a [Docker Compose file](/reference/compose-file/_index.md) if you want to re-create your containers with the same configuration after re-installation.
|
||||
|
||||
## Save your data
|
||||
|
||||
|
|
@ -23,12 +23,12 @@ computer, for example.
|
|||
Also note that filesystem changes in volume that are attached to the
|
||||
container are not included in the image, and must be backed up separately.
|
||||
|
||||
If you used a [named volume](/manuals/engine/storage/index.md#more-details-about-mount-types) to store container data, such as databases, refer to the [back up, restore, or migrate data volumes](/manuals/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section.
|
||||
If you used a [named volume](/manuals/engine/storage/_index.md#more-details-about-mount-types) to store container data, such as databases, refer to the [back up, restore, or migrate data volumes](/manuals/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section.
|
||||
|
||||
2. Use [`docker push`](/reference/cli/docker/image/push.md) to push any
|
||||
images you have built locally and want to keep to the [Docker Hub registry](../docker-hub/index.md).
|
||||
images you have built locally and want to keep to the [Docker Hub registry](../docker-hub/_index.md).
|
||||
|
||||
Make sure to configure the [repository's visibility as "private"](../docker-hub/repos/index.md)
|
||||
Make sure to configure the [repository's visibility as "private"](../docker-hub/repos/_index.md)
|
||||
for images that should not be publicly accessible.
|
||||
|
||||
Alternatively, use [`docker image save -o images.tar image1 [image2 ...]`](/reference/cli/docker/image/save.md)
|
||||
|
|
@ -46,6 +46,6 @@ and [install a different version](release-notes.md) or reset Docker Desktop to f
|
|||
to restore previously saved images.
|
||||
|
||||
2. Re-create your containers if needed, using [`docker run`](/reference/cli/docker/container/run.md),
|
||||
or [Docker Compose](/manuals/compose/index.md).
|
||||
or [Docker Compose](/manuals/compose/_index.md).
|
||||
|
||||
Refer to the [backup, restore, or migrate data volumes](/manuals/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section to restore volume data.
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ aliases:
|
|||
- /desktop/enterprise/troubleshoot/windows-issues/
|
||||
---
|
||||
|
||||
Docker Desktop Enterprise (DDE) has been deprecated and is no longer in active development. Please use [Docker Desktop](../index.md) Community instead.
|
||||
Docker Desktop Enterprise (DDE) has been deprecated and is no longer in active development. Please use [Docker Desktop](../_index.md) Community instead.
|
||||
|
||||
If you are an existing DDE customer, use our [Support form](https://hub.docker.com/support/desktop/) to request a transition to one of our new [subscription plans](https://www.docker.com/pricing).
|
||||
|
||||
|
|
|
|||
|
|
@ -17,13 +17,13 @@ cannot access features that require an active internet
|
|||
connection. Additionally, any functionality that requires you to sign in won't work while using Docker Desktop offline or in air-gapped environments.
|
||||
This includes:
|
||||
|
||||
- The resources in the [Learning Center](../use-desktop/index.md)
|
||||
- The resources in the [Learning Center](../use-desktop/_index.md)
|
||||
- Pulling or pushing an image to Docker Hub
|
||||
- [Image Access Management](../../security/for-developers/access-tokens.md)
|
||||
- [Static vulnerability scanning](../../docker-hub/vulnerability-scanning.md)
|
||||
- Viewing remote images in the Docker Dashboard
|
||||
- Setting up [Dev Environments](../dev-environments/index.md)
|
||||
- Docker Build when using [BuildKit](/manuals/build/buildkit/index.md#getting-started).
|
||||
- Setting up [Dev Environments](../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](../kubernetes.md) (Images are download when you enable Kubernetes for the first time)
|
||||
- Checking for updates
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ In large enterprises where admin access is restricted, administrators can [enfor
|
|||
|
||||
- Authenticated users also get a higher pull rate limit compared to anonymous users. For example, if you are authenticated, you get 200 pulls per 6 hour period, compared to 100 pulls per 6 hour period per IP address for anonymous users. For more information, see [Download rate limit](../docker-hub/download-rate-limit.md).
|
||||
|
||||
- Improve your organization’s security posture for containerized development by taking advantage of [Hardened Desktop](/manuals/security/for-admins/hardened-desktop/index.md).
|
||||
- Improve your organization’s security posture for containerized development by taking advantage of [Hardened Desktop](/manuals/security/for-admins/hardened-desktop/_index.md).
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
|
|
@ -107,6 +107,6 @@ docker.io/molly/privateimage:latest
|
|||
|
||||
## What's next?
|
||||
|
||||
- [Explore Docker Desktop](use-desktop/index.md) and its features.
|
||||
- [Explore Docker Desktop](use-desktop/_index.md) and its features.
|
||||
- Change your Docker Desktop settings
|
||||
- [Browse common FAQs](faqs/general.md)
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Docker Desktop for Windows supports WSL 2 GPU Paravirtualization (GPU-PV) on NVI
|
|||
- Up to date Windows 10 or Windows 11 installation
|
||||
- [Up to date drivers](https://developer.nvidia.com/cuda/wsl) from NVIDIA supporting WSL 2 GPU Paravirtualization
|
||||
- The latest version of the WSL 2 Linux kernel. Use `wsl --update` on the command line
|
||||
- To make sure the [WSL 2 backend is turned on](wsl/index.md#turn-on-docker-desktop-wsl-2) in Docker Desktop
|
||||
- To make sure the [WSL 2 backend is turned on](wsl/_index.md#turn-on-docker-desktop-wsl-2) in Docker Desktop
|
||||
|
||||
To validate that everything works as expected, execute a `docker run` command with the `--gpus=all` flag. For example, the following will run a short benchmark on your GPU:
|
||||
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@ $ sudo pacman -S gnome-terminal
|
|||
|
||||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
|
||||
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
|
|
|
|||
|
|
@ -88,7 +88,7 @@ Don't forget to substitute `<arch>` with the architecture you want.
|
|||
|
||||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
|
||||
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ Don't forget to substitute `<arch>` with the architecture you want.
|
|||
|
||||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
|
||||
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ The `install` command accepts the following flags:
|
|||
- `--accept-license`: Accepts the [Docker Subscription Service Agreement](https://www.docker.com/legal/docker-subscription-service-agreement) now, rather than requiring it to be accepted when the application is first run.
|
||||
- `--allowed-org=<org name>`: Requires the user to sign in and be part of the specified Docker Hub organization when running the application
|
||||
- `--user=<username>`: Performs the privileged configurations once during installation. This removes the need for the user to grant root privileges on first run. For more information, see [Privileged helper permission requirements](../mac/permission-requirements.md#permission-requirements). To find the username, enter `ls /Users` in the CLI.
|
||||
- `--admin-settings`: Automatically creates an `admin-settings.json` file which is used by administrators to control certain Docker Desktop settings on client machines within their organization. For more information, see [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md).
|
||||
- `--admin-settings`: Automatically creates an `admin-settings.json` file which is used by administrators to control certain Docker Desktop settings on client machines within their organization. For more information, see [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md).
|
||||
- It must be used together with the `--allowed-org=<org name>` flag.
|
||||
- For example:
|
||||
`--allowed-org=<org name> --admin-settings='{"configurationFileVersion": 2, "enhancedContainerIsolation": {"value": true, "locked": false}}'`
|
||||
|
|
@ -128,7 +128,7 @@ The `install` command accepts the following flags:
|
|||
|
||||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- [Get started with Docker](/get-started/introduction/_index.md).
|
||||
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
|
||||
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how
|
||||
to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
|
||||
|
|
|
|||
|
|
@ -138,7 +138,7 @@ $ sudo dnf install ./docker-desktop-<arch>-rhel.rpm
|
|||
|
||||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
|
||||
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ Don't forget to substitute `<arch>` with the architecture you want.
|
|||
|
||||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- Take a look at the [Docker workshop](/get-started/workshop/_index.md) to learn how to build an image and run it as a containerized application.
|
||||
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
|
||||
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
|
||||
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
|
||||
- [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.
|
||||
|
|
|
|||
|
|
@ -215,7 +215,7 @@ The `install` command accepts the following flags:
|
|||
- `--allowed-org=<org name>`: Requires the user to sign in and be part of the specified Docker Hub organization when running the application
|
||||
- `--backend=<backend name>`: Selects the default backend to use for Docker Desktop, `hyper-v`, `windows` or `wsl-2` (default)
|
||||
- `--installation-dir=<path>`: Changes the default installation location (`C:\Program Files\Docker\Docker`)
|
||||
- `--admin-settings`: Automatically creates an `admin-settings.json` file which is used by admins to control certain Docker Desktop settings on client machines within their organization. For more information, see [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md).
|
||||
- `--admin-settings`: Automatically creates an `admin-settings.json` file which is used by admins to control certain Docker Desktop settings on client machines within their organization. For more information, see [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md).
|
||||
- It must be used together with the `--allowed-org=<org name>` flag.
|
||||
- For example:
|
||||
|
||||
|
|
@ -276,7 +276,7 @@ Docker Desktop does not start automatically after installation. To start Docker
|
|||
|
||||
- Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
|
||||
- [Get started with Docker](/get-started/introduction/_index.md).
|
||||
- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
|
||||
- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
|
||||
- [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, and
|
||||
how to get support.
|
||||
- [FAQs](../faqs/general.md) provide answers to frequently asked questions.
|
||||
|
|
|
|||
|
|
@ -226,7 +226,7 @@ Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
### New
|
||||
|
||||
- **Docker Desktop Dashboard:** The new Docker Desktop **Dashboard** provides a user-friendly interface which enables you to interact with containers and applications, and manage the lifecycle of your applications directly from the UI. In addition, it allows you to access the logs, view container details, and monitor resource utilization to explore the container behavior.
|
||||
For detailed information about the new Dashboard UI, see [Docker Desktop Dashboard](../index.md).
|
||||
For detailed information about the new Dashboard UI, see [Docker Desktop Dashboard](../_index.md).
|
||||
|
||||
- Introduced a new user interface for the Docker Desktop **Preferences** menu.
|
||||
- The Restart, Reset, and Uninstall options are now available on the **Troubleshoot** menu.
|
||||
|
|
@ -340,7 +340,7 @@ Note that you must sign in and create a Docker ID in order to download Docker De
|
|||
Docker Desktop Community 2.1.0.0 contains the following experimental features.
|
||||
|
||||
* Docker App: Docker App is a CLI plugin that helps configure, share, and install applications.
|
||||
* Docker Buildx: Docker Buildx is a CLI plugin for extended build capabilities with BuildKit. For more information, see the [Build page](/manuals/build/index.md).
|
||||
* Docker Buildx: Docker Buildx is a CLI plugin for extended build capabilities with BuildKit. For more information, see the [Build page](/manuals/build/_index.md).
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
|
|
|
|||
|
|
@ -244,7 +244,7 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
|
||||
### Known issues
|
||||
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the [WSL 2 backend](../wsl/index.md).
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the [WSL 2 backend](../wsl/_index.md).
|
||||
|
||||
**WSL 2**
|
||||
|
||||
|
|
@ -284,7 +284,7 @@ Docker Desktop 2.4.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
|
||||
### Known issues
|
||||
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the experimental [WSL backend](../wsl/index.md).
|
||||
- Some CLI commands fail if you are running Docker Desktop in the experimental Linux Containers on Windows (LCOW) mode. As alternatives, we recommend running either traditional Linux containers, or the experimental [WSL backend](../wsl/_index.md).
|
||||
- It is not possible to resize the disk image using the Docker Desktop **Settings** UI. If you would like to update the size of the disk image (for example, to 128 GB), run the following command in PowerShell:
|
||||
|
||||
```powershell
|
||||
|
|
@ -346,9 +346,9 @@ Docker Desktop 2.2.0.0 contains a Kubernetes upgrade. Your local Kubernetes clus
|
|||
### New
|
||||
|
||||
- **Docker Desktop Dashboard:** The new Docker Desktop **Dashboard** provides a user-friendly interface which enables you to interact with containers and applications, and manage the lifecycle of your applications directly from the UI. In addition, it allows you to access the logs, view container details, and monitor resource utilization to explore the container behavior.
|
||||
For detailed information about the new Dashboard UI, see [Docker Desktop Dashboard](../index.md).
|
||||
For detailed information about the new Dashboard UI, see [Docker Desktop Dashboard](../_index.md).
|
||||
|
||||
- **WSL 2 backend:** The experimental Docker Desktop WSL 2 backend architecture introduces support for Kubernetes, provides an updated Docker daemon, offers VPN-friendly networking, and additional features. For more information, see [Docker Desktop WSL 2 backend](../wsl/index.md).
|
||||
- **WSL 2 backend:** The experimental Docker Desktop WSL 2 backend architecture introduces support for Kubernetes, provides an updated Docker daemon, offers VPN-friendly networking, and additional features. For more information, see [Docker Desktop WSL 2 backend](../wsl/_index.md).
|
||||
|
||||
- **New file sharing implementation:** Docker Desktop introduces a new file sharing implementation that replaces Samba, CIFS, and Hyper-V networking. The new implementation offers improved I/O performance. Additionally, when using the new file system:
|
||||
|
||||
|
|
@ -468,7 +468,7 @@ Note that you must sign in and create a Docker ID in order to download Docker De
|
|||
Docker Desktop Community 2.1.0.0 contains the following experimental features:
|
||||
|
||||
* Docker App: Docker App is a CLI plugin that helps configure, share, and install applications.
|
||||
* Docker Buildx: Docker Buildx is a CLI plugin for extended build capabilities with BuildKit. For more information, see the [Build page](/manuals/build/index.md).
|
||||
* Docker Buildx: Docker Buildx is a CLI plugin for extended build capabilities with BuildKit. For more information, see the [Build page](/manuals/build/_index.md).
|
||||
|
||||
### Bug fixes and minor changes
|
||||
|
||||
|
|
|
|||
|
|
@ -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](../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. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments/_index.md).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -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](../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. 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](/manuals/compose/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](../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. 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](/manuals/compose/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.
|
||||
|
||||
|
|
@ -130,7 +130,7 @@ This page contains release notes for Docker Desktop for Mac 3.x.
|
|||
|
||||
### Deprecation
|
||||
|
||||
- Docker Desktop no longer installs Notary. You can now use [Docker Content Trust](/manuals/engine/security/trust/index.md) for image signing.
|
||||
- Docker Desktop no longer installs Notary. You can now use [Docker Content Trust](/manuals/engine/security/trust/_index.md) for image signing.
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
|
|||
|
|
@ -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](../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. For more information and for instructions on how to use Dev Environments, see [Development Environments Preview](../dev-environments/_index.md).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
@ -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](../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. 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](/manuals/compose/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](../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. 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](/manuals/compose/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.
|
||||
|
||||
|
|
|
|||
|
|
@ -1126,7 +1126,7 @@ TCP connection is idle for more than five minutes (related to
|
|||
|
||||
- Add daemon options validation
|
||||
- Diagnose can be cancelled & Improved help information. Fixes [docker/for-mac#1134](https://github.com/docker/for-mac/issues/1134), [docker/for-mac#1474](https://github.com/docker/for-mac/issues/1474)
|
||||
- Support paging of Docker Cloud [repositories](../../docker-hub/repos/index.md) and [organizations](../../admin/organization/orgs.md). Fixes [docker/for-mac#1538](https://github.com/docker/for-mac/issues/1538)
|
||||
- Support paging of Docker Cloud [repositories](../../docker-hub/repos/_index.md) and [organizations](../../admin/organization/orgs.md). Fixes [docker/for-mac#1538](https://github.com/docker/for-mac/issues/1538)
|
||||
|
||||
### Docker Community Edition 17.06.1-ce-mac20, 2017-07-18
|
||||
|
||||
|
|
@ -1979,7 +1979,7 @@ events or unexpected unmounts.
|
|||
|
||||
**Bug fixes and minor changes**
|
||||
|
||||
* Documentation moved to [/desktop/mac/](../index.md)
|
||||
* Documentation moved to [/desktop/mac/](../_index.md)
|
||||
* Allow non-admin users to launch the app for the first time (using admin creds)
|
||||
* Prompt non-admin users for admin password when needed in Preferences
|
||||
* Fixed download links, documentation links
|
||||
|
|
|
|||
|
|
@ -624,7 +624,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
|
||||
To access the Dashboard UI, select the Docker menu from the system tray and then click **Dashboard**.
|
||||
|
||||
- **WSL 2 backend:** The new Docker Desktop WSL 2 backend replaces the Docker Desktop WSL 2 Tech Preview. The WSL 2 backend architecture introduces support for Kubernetes, provides an updated Docker daemon, offers VPN-friendly networking, and additional features. For more information, see [Docker Desktop WSL 2 backend](../wsl/index.md).
|
||||
- **WSL 2 backend:** The new Docker Desktop WSL 2 backend replaces the Docker Desktop WSL 2 Tech Preview. The WSL 2 backend architecture introduces support for Kubernetes, provides an updated Docker daemon, offers VPN-friendly networking, and additional features. For more information, see [Docker Desktop WSL 2 backend](../wsl/_index.md).
|
||||
|
||||
- **New file sharing implementation:** Docker Desktop introduces a new file sharing implementation which uses gRPC, FUSE, and Hypervisor sockets instead of Samba, CIFS, and Hyper-V networking. The new implementation offers improved I/O performance. Additionally, when using the new file system:
|
||||
|
||||
|
|
@ -699,7 +699,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
|
|||
|
||||
#### New
|
||||
|
||||
- [Docker Desktop WSL 2 Tech Preview](../wsl/index.md)
|
||||
- [Docker Desktop WSL 2 Tech Preview](../wsl/_index.md)
|
||||
|
||||
#### Bug fixes and minor changes
|
||||
|
||||
|
|
|
|||
|
|
@ -207,7 +207,7 @@ For more information, see [microsoft/WSL#11794](https://github.com/microsoft/WSL
|
|||
|
||||
- Improved instructions for `watch` in the Compose File Viewer
|
||||
- Added support for Golang projects that don't have dependencies in Docker Init. Addresses [docker/roadmap#611](https://github.com/docker/roadmap/issues/611)
|
||||
- [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md) now lets admins set the default value to `ProxyEnableKerberosNTLM`.
|
||||
- [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md) now lets admins set the default value to `ProxyEnableKerberosNTLM`.
|
||||
- Removed a temporary compatibility fix for older versions of Visual Studio Code.
|
||||
- Builds view:
|
||||
- Changed icon for imported build record to a "files" icon.
|
||||
|
|
@ -518,7 +518,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st
|
|||
|
||||
### New
|
||||
|
||||
- [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md) now allows admins to set the default file-sharing implementation and specify which paths developer can add file shares to.
|
||||
- [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md) now allows admins to set the default file-sharing implementation and specify which paths developer can add file shares to.
|
||||
- Added support for `socks5://` HTTP and HTTPS proxy URLs when the [`SOCKS` proxy support beta feature](networking.md) is enabled.
|
||||
- Users can now filter volumes to see which ones are in use in the **Volumes** tab.
|
||||
|
||||
|
|
@ -1131,7 +1131,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st
|
|||
|
||||
#### For all platforms
|
||||
|
||||
- [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md) now lets you turn off Docker Extensions for your organisation.
|
||||
- [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md) now lets you turn off Docker Extensions for your organisation.
|
||||
- Fixed a bug where turning on Kubernetes from the UI failed when the system was paused.
|
||||
- Fixed a bug where turning on Wasm from the UI failed when the system was paused.
|
||||
- Bind mounts are now shown when you [inspect a container](use-desktop/container.md).
|
||||
|
|
@ -1368,8 +1368,8 @@ This can be resolved by adding the user to the **docker-users** group. Before st
|
|||
|
||||
#### For all platforms
|
||||
|
||||
- [Docker Scout CLI](../scout/index.md#docker-scout-cli) can now compare two images and display packages and vulnerabilities differences. This command is in [Early Access](../release-lifecycle.md) and might change in the future.
|
||||
- [Docker Scout CLI](../scout/index.md#docker-scout-cli) now displays base image update and remediation recommendations using `docker scout recommendations`. It also displays a short overview of an image using `docker scout quickview` commands.
|
||||
- [Docker Scout CLI](../scout/_index.md#docker-scout-cli) can now compare two images and display packages and vulnerabilities differences. This command is in [Early Access](../release-lifecycle.md) and might change in the future.
|
||||
- [Docker Scout CLI](../scout/_index.md#docker-scout-cli) now displays base image update and remediation recommendations using `docker scout recommendations`. It also displays a short overview of an image using `docker scout quickview` commands.
|
||||
- You can now search for extensions direct from the Marketplace, as well as using **Global Search**.
|
||||
- Fixed a bug where `docker buildx` container builders would lose access to the network after 24hrs.
|
||||
- Reduced how often users are prompted for feedback on Docker Desktop.
|
||||
|
|
@ -1432,8 +1432,8 @@ This can be resolved by adding the user to the **docker-users** group. Before st
|
|||
|
||||
### New
|
||||
|
||||
- Docker Desktop now ships with Docker Scout. Pull and view analysis for images from Docker Hub and Artifactory repositories, get base image updates and recommended tags and digests, and filter your images on vulnerability information. To learn more, see [Docker Scout](../scout/index.md).
|
||||
- `docker scan` has been replaced by `docker scout`. See [Docker Scout CLI](../scout/index.md#docker-scout-cli), for more information.
|
||||
- Docker Desktop now ships with Docker Scout. Pull and view analysis for images from Docker Hub and Artifactory repositories, get base image updates and recommended tags and digests, and filter your images on vulnerability information. To learn more, see [Docker Scout](../scout/_index.md).
|
||||
- `docker scan` has been replaced by `docker scout`. See [Docker Scout CLI](../scout/_index.md#docker-scout-cli), for more information.
|
||||
- You can now discover extensions that have been autonomously published in the Extensions Marketplace. For more information on self-published extensions, see [Marketplace Extensions](/manuals/extensions/marketplace.md).
|
||||
- **Container File Explorer** is available as an experimental feature. Debug the filesystem within your containers straight from the GUI.
|
||||
- You can now search for volumes in **Global Search**.
|
||||
|
|
@ -1615,7 +1615,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st
|
|||
|
||||
- Substantial performance improvements for macOS users with the option of enabling the new VirtioFS file sharing technology. Available for macOS 12.5 and above.
|
||||
- Docker Desktop for Mac no longer needs to install the privileged helper process `com.docker.vmnetd` on install or on the first run. For more information see [Permission requirements for Mac](https://docs.docker.com/desktop/mac/permission-requirements/).
|
||||
- Added [WebAssembly capabilities](wasm/index.md). Use with the [containerd integration](containerd/index.md).
|
||||
- Added [WebAssembly capabilities](wasm/_index.md). Use with the [containerd integration](containerd/_index.md).
|
||||
- Improved the descriptions for beta and experimental settings to clearly explain the differences and how people can access them.
|
||||
- Available disk space of VM now displays in the footer of Docker Dashboard for Mac and Linux.
|
||||
- A disk space warning now displays in the footer if available space is below 3GB.
|
||||
|
|
@ -1763,7 +1763,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st
|
|||
|
||||
### New
|
||||
|
||||
- Two new security features have been introduced for Docker Business users, Settings Management and Enhanced Container Isolation. Read more about Docker Desktop’s new [Hardened Docker Desktop security model](/manuals/security/for-admins/hardened-desktop/index.md).
|
||||
- Two new security features have been introduced for Docker Business users, Settings Management and Enhanced Container Isolation. Read more about Docker Desktop’s new [Hardened Docker Desktop security model](/manuals/security/for-admins/hardened-desktop/_index.md).
|
||||
- Added the new Dev Environments CLI `docker dev`, so you can create, list, and run Dev Envs via command line. Now it's easier to integrate Dev Envs into custom scripts.
|
||||
- Docker Desktop can now be installed to any drive and folder using the `--installation-dir`. Partially addresses [docker/roadmap#94](https://github.com/docker/roadmap/issues/94).
|
||||
|
||||
|
|
@ -2460,7 +2460,7 @@ Installing Docker Desktop 4.5.0 from scratch has a bug which defaults Docker Des
|
|||
### New
|
||||
|
||||
- Easy, Secure sign in with Auth0 and Single Sign-on
|
||||
- Single Sign-on: Users with a Docker Business subscription can now configure SSO to authenticate using their identity providers (IdPs) to access Docker. For more information, see [Single Sign-on](../security/for-admins/single-sign-on/index.md).
|
||||
- Single Sign-on: Users with a Docker Business subscription can now configure SSO to authenticate using their identity providers (IdPs) to access Docker. For more information, see [Single Sign-on](../security/for-admins/single-sign-on/_index.md).
|
||||
- Signing in to Docker Desktop now takes you through the browser so that you get all the benefits of auto-filling from password managers.
|
||||
|
||||
### Upgrades
|
||||
|
|
@ -2472,7 +2472,7 @@ Installing Docker Desktop 4.5.0 from scratch has a bug which defaults Docker Des
|
|||
|
||||
### Security
|
||||
|
||||
- Fixed [CVE-2021-45449](../security/index.md#cve-2021-45449) that affects users currently on Docker Desktop version 4.3.0 or 4.3.1.
|
||||
- Fixed [CVE-2021-45449](../security/_index.md#cve-2021-45449) that affects users currently on Docker Desktop version 4.3.0 or 4.3.1.
|
||||
|
||||
Docker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user's machine during login.
|
||||
This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access to this data would require having access to the user’s local files.
|
||||
|
|
@ -2512,7 +2512,7 @@ This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user
|
|||
|
||||
### Security
|
||||
|
||||
- Fixed [CVE-2021-45449](../security/index.md#cve-2021-45449) that affects users currently on Docker Desktop version 4.3.0 or 4.3.1.
|
||||
- Fixed [CVE-2021-45449](../security/_index.md#cve-2021-45449) that affects users currently on Docker Desktop version 4.3.0 or 4.3.1.
|
||||
|
||||
Docker Desktop version 4.3.0 and 4.3.1 has a bug that may log sensitive information (access token or password) on the user's machine during login.
|
||||
This only affects users if they are on Docker Desktop 4.3.0, 4.3.1 and the user has logged in while on 4.3.0, 4.3.1. Gaining access to this data would require having access to the user’s local files.
|
||||
|
|
@ -2739,7 +2739,7 @@ The updated [Docker Subscription Service Agreement](https://www.docker.com/legal
|
|||
- **No changes** to Docker Engine or any other upstream **open source** Docker or Moby project.
|
||||
|
||||
To understand how these changes affect you, read the [FAQs](https://www.docker.com/pricing/faq).
|
||||
For more information, see [Docker subscription overview](../subscription/index.md).
|
||||
For more information, see [Docker subscription overview](../subscription/_index.md).
|
||||
|
||||
### Upgrades
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ If you choose the integrated terminal, you can run commands in a running contain
|
|||
execution attacks.
|
||||
|
||||
- {{< badge color=blue text="Windows only" >}}**Use the WSL 2 based engine**. WSL 2 provides better performance than the
|
||||
Hyper-V backend. For more information, see [Docker Desktop WSL 2 backend](/manuals/desktop/wsl/index.md).
|
||||
Hyper-V backend. For more information, see [Docker Desktop WSL 2 backend](/manuals/desktop/wsl/_index.md).
|
||||
|
||||
- {{< badge color=blue text="Windows only" >}}**Add the `*.docker.internal` names to the host's `/etc/hosts` file (Password required)**. Lets you resolve `*.docker.internal` DNS names from both the host and your containers.
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ If you choose the integrated terminal, you can run commands in a running contain
|
|||
troubleshoot the application. Clear the checkbox to opt out. Docker may
|
||||
periodically prompt you for more information.
|
||||
|
||||
- **Use Enhanced Container Isolation**. Select to enhance security by preventing containers from breaching the Linux VM. For more information, see [Enhanced Container Isolation](/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/index.md).
|
||||
- **Use Enhanced Container Isolation**. Select to enhance security by preventing containers from breaching the Linux VM. For more information, see [Enhanced Container Isolation](/manuals/security/for-admins/hardened-desktop/enhanced-container-isolation/_index.md).
|
||||
> [!NOTE]
|
||||
>
|
||||
> This setting is only available if you are signed in to Docker Desktop and have a Docker Business subscription.
|
||||
|
|
@ -247,7 +247,7 @@ To set a different proxy for Docker Desktop, turn on **Manual proxy configuratio
|
|||
upstream proxy URL of the form `http://proxy:port` or `https://proxy:port`.
|
||||
|
||||
To prevent developers from accidentally changing the proxy settings, see
|
||||
[Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/index.md#what-features-can-i-configure-with-settings-management).
|
||||
[Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md#what-features-can-i-configure-with-settings-management).
|
||||
|
||||
The HTTPS proxy settings used for scanning images are set using the `HTTPS_PROXY` environment variable.
|
||||
|
||||
|
|
@ -304,7 +304,7 @@ to set Ubuntu as your default WSL distro, run `wsl --set-default ubuntu`).
|
|||
You can also select any additional distributions you would like to enable the WSL 2 integration on.
|
||||
|
||||
For more details on configuring Docker Desktop to use WSL 2, see
|
||||
[Docker Desktop WSL 2 backend](/manuals/desktop/wsl/index.md).
|
||||
[Docker Desktop WSL 2 backend](/manuals/desktop/wsl/_index.md).
|
||||
|
||||
## Docker Engine
|
||||
|
||||
|
|
@ -443,7 +443,7 @@ Use the **Extensions** tab to:
|
|||
- **Allow only extensions distributed through the Docker Marketplace**
|
||||
- **Show Docker Extensions system containers**
|
||||
|
||||
For more information about Docker extensions, see [Extensions](/manuals/extensions/index.md).
|
||||
For more information about Docker extensions, see [Extensions](/manuals/extensions/_index.md).
|
||||
|
||||
## Features in development
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ The **Troubleshoot** page contains the following options:
|
|||
|
||||
- **Restart Docker Desktop**.
|
||||
|
||||
- **Get support**. Users with a paid Docker subscription can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see [Diagnose and feedback](#diagnose) and [Support](../../support/index.md).
|
||||
- **Get support**. Users with a paid Docker subscription can use this option to send a support request. Other users can use this option to diagnose any issues in Docker Desktop. For more information, see [Diagnose and feedback](#diagnose) and [Support](../../support/_index.md).
|
||||
|
||||
- **Reset Kubernetes cluster**. Select to delete all stacks and Kubernetes resources. For more information, see [Kubernetes](/manuals/desktop/settings.md#kubernetes).
|
||||
|
||||
|
|
@ -64,7 +64,7 @@ This opens the in-app **Support** page and starts collecting the diagnostics.
|
|||
- If you have a paid Docker subscription, select **Contact Support**. This opens the [Docker Desktop support](https://hub.docker.com/support/desktop/) form. Fill in the information required and add the ID you copied in step three to the **Diagnostics ID** field. Then, select **Submit** to request Docker Desktop support.
|
||||
> [!NOTE]
|
||||
>
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../../support/index.md).
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../../support/_index.md).
|
||||
- If you don't have a paid Docker subscription, select **Report a Bug** to open a new Docker Desktop issue on GitHub. Complete the information required and ensure you add the diagnostic ID you copied in step three.
|
||||
|
||||
### Diagnose from an error message
|
||||
|
|
@ -75,7 +75,7 @@ This opens the in-app **Support** page and starts collecting the diagnostics.
|
|||
- If you have a paid Docker subscription, you can [contact support](https://hub.docker.com/support/desktop/). Fill in the information required and add the ID you copied in step two to the **Diagnostics ID** field. Then, select **Submit** to request Docker Desktop support.
|
||||
> [!NOTE]
|
||||
>
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../../support/index.md).
|
||||
> You must be signed in to Docker Desktop to access the support form. For information on what's covered as part of Docker Desktop support, see [Support](../../support/_index.md).
|
||||
- If you don't have a paid Docker subscription, you can open a new Docker Desktop issue on GitHub for [Mac](https://github.com/docker/for-mac/issues), [Windows](https://github.com/docker/for-win/issues), or [Linux](https://github.com/docker/for-linux/issues). Complete the information required and ensure you add the diagnostic ID you copied in step two.
|
||||
|
||||
### Diagnose from the terminal
|
||||
|
|
|
|||
|
|
@ -286,7 +286,7 @@ In the subsequent screen, verify that Hyper-V is enabled.
|
|||
|
||||
#### Virtualization must be turned on
|
||||
|
||||
In addition to [Hyper-V](#hyper-v) or [WSL 2](../wsl/index.md), virtualization must be turned on. Check the
|
||||
In addition to [Hyper-V](#hyper-v) or [WSL 2](../wsl/_index.md), virtualization must be turned on. Check the
|
||||
Performance tab on the Task Manager. Alternatively, you can type 'systeminfo' into your terminal. If you see 'Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed', then virtualization is enabled.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -36,8 +36,8 @@ Docker Hub is also where you can go to [change your Docker account settings and
|
|||
|
||||
{{< tabs >}}
|
||||
{{< tab name="What key features are included in Docker Hub?" >}}
|
||||
* [Repositories](../docker-hub/repos/index.md): Push and pull container images.
|
||||
* [Builds](builds/index.md): Automatically build container images from
|
||||
* [Repositories](../docker-hub/repos/_index.md): Push and pull container images.
|
||||
* [Builds](builds/_index.md): Automatically build container images from
|
||||
GitHub and Bitbucket and push them to Docker Hub.
|
||||
* [Webhooks](webhooks.md): Trigger actions after a successful push
|
||||
to a repository to integrate Docker Hub with other services.
|
||||
|
|
@ -48,7 +48,7 @@ GitHub and Bitbucket and push them to Docker Hub.
|
|||
* [Create and manage teams and organizations](orgs.md)
|
||||
* [Create a company](../admin/company/new-company.md)
|
||||
* [Enforce sign in](../security/for-admins/enforce-sign-in/_index.md)
|
||||
* Set up [SSO](../security/for-admins/single-sign-on/index.md) and [SCIM](../security/for-admins/provisioning/scim.md)
|
||||
* Set up [SSO](../security/for-admins/single-sign-on/_index.md) and [SCIM](../security/for-admins/provisioning/scim.md)
|
||||
* Use [Group mapping](group-mapping.md)
|
||||
* [Carry out domain audits](domain-audit.md)
|
||||
* [Use Image Access Management](/manuals/security/for-admins/hardened-desktop/image-access-management.md) to control developers' access to certain types of images
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ aliases:
|
|||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/index.md).
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
This page contains information on:
|
||||
- [Configuring Automated builds](#configure-automated-builds)
|
||||
|
|
@ -227,7 +227,7 @@ sources. For example, you might have
|
|||
|
||||
Autobuilds use the BuildKit build system by default. If you want to use the legacy
|
||||
Docker build system, add the [environment variable](index.md#environment-variables-for-builds)
|
||||
`DOCKER_BUILDKIT=0`. Refer to the [BuildKit](/manuals/build/buildkit/index.md)
|
||||
`DOCKER_BUILDKIT=0`. Refer to the [BuildKit](/manuals/build/buildkit/_index.md)
|
||||
page for more information on BuildKit.
|
||||
|
||||
## Autobuild for teams
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ title: Advanced options for Autobuild and Autotest
|
|||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/index.md).
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
The following options allow you to customize your automated build and automated
|
||||
test processes.
|
||||
|
|
|
|||
|
|
@ -7,10 +7,10 @@ title: Automated repository tests
|
|||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/index.md).
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
Docker Hub can automatically test changes to your source code repositories
|
||||
using containers. You can enable `Autotest` on [any Docker Hub repository](../repos/index.md)
|
||||
using containers. You can enable `Autotest` on [any Docker Hub repository](../repos/_index.md)
|
||||
to run tests on each pull request to the source code repository to create a
|
||||
continuous integration testing service.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ title: How Automated builds work
|
|||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/index.md).
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
Docker Hub can automatically build images from source code in an external
|
||||
repository and automatically push the built image to your Docker repositories.
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ aliases:
|
|||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/index.md).
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
To automate building and testing of your images, you link to your hosted source
|
||||
code service to Docker Hub so that it can access your source code
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ keywords: autobuilds, automated, docker hub, registry
|
|||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/index.md).
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
## Cancel or retry a build
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ tags: [ Troubleshooting ]
|
|||
> [!NOTE]
|
||||
>
|
||||
> Automated builds require a
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/index.md).
|
||||
> [Docker Pro, Team, or Business subscription](../../subscription/_index.md).
|
||||
|
||||
## Failing builds
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ You've created your first repository.
|
|||
|
||||
You need to download Docker Desktop to build, push, and pull container images.
|
||||
|
||||
1. Download and install [Docker Desktop](/manuals/desktop/index.md).
|
||||
1. Download and install [Docker Desktop](/manuals/desktop/_index.md).
|
||||
|
||||
2. Sign in to Docker Desktop using the Docker ID you created in step one.
|
||||
|
||||
|
|
@ -142,7 +142,7 @@ You've successfully:
|
|||
### Next steps
|
||||
|
||||
- Create an [organization](orgs.md) to use Docker Hub with your team.
|
||||
- Automatically build container images from code through [builds](builds/index.md).
|
||||
- Automatically build container images from code through [builds](builds/_index.md).
|
||||
- [Explore](https://hub.docker.com/explore) official & publisher images.
|
||||
- [Upgrade your subscription](https://www.docker.com/pricing) to push additional private Docker images to
|
||||
Docker Hub.
|
||||
|
|
|
|||
|
|
@ -133,7 +133,7 @@ The updated [Docker Subscription Service Agreement](https://www.docker.com/legal
|
|||
- The existing Docker Free subscription has been renamed **Docker Personal**.
|
||||
- **No changes** to Docker Engine or any other upstream **open source** Docker or Moby project.
|
||||
|
||||
To understand how these changes affect you, read the [FAQs](https://www.docker.com/pricing/faq). For more information, see [Docker subscription overview](../subscription/index.md).
|
||||
To understand how these changes affect you, read the [FAQs](https://www.docker.com/pricing/faq). For more information, see [Docker subscription overview](../subscription/_index.md).
|
||||
|
||||
## 2021-05-05
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ You can now specify any email address to receive billing-related emails for your
|
|||
|
||||
To change the email address receiving billing-related emails, log into Docker Hub and navigate to the **Billing** tab of your organization. Select **Payment Methods** > **Billing Information**. Enter the new email address that you'd like to use in the **Email** field. Click **Update** for the changes to take effect.
|
||||
|
||||
For details on how to update your billing information, see [Update billing information](../billing/index.md).
|
||||
For details on how to update your billing information, see [Update billing information](../billing/_index.md).
|
||||
|
||||
## 2021-03-22
|
||||
|
||||
|
|
@ -179,7 +179,7 @@ For more information about this feature and for instructions on how to use it, s
|
|||
|
||||
### New feature
|
||||
|
||||
The **Repositories** view now shows which images have gone stale because they haven't been pulled or pushed recently. For more information, see [repository tags](repos/access/index.md#view-repository-tags).
|
||||
The **Repositories** view now shows which images have gone stale because they haven't been pulled or pushed recently. For more information, see [repository tags](repos/access/_index.md#view-repository-tags).
|
||||
|
||||
## 2020-10-07
|
||||
|
||||
|
|
@ -191,7 +191,7 @@ Docker introduces Hub Vulnerability Scanning which enables you to automatically
|
|||
|
||||
### New features
|
||||
|
||||
* Docker has announced a new, per-seat pricing model to accelerate developer workflows for cloud-native development. The previous private repository/concurrent autobuild-based plans have been replaced with new **Pro** and **Team** plans that include unlimited private repositories. For more information, see [Docker subscription](../subscription/index.md).
|
||||
* Docker has announced a new, per-seat pricing model to accelerate developer workflows for cloud-native development. The previous private repository/concurrent autobuild-based plans have been replaced with new **Pro** and **Team** plans that include unlimited private repositories. For more information, see [Docker subscription](../subscription/_index.md).
|
||||
|
||||
* Docker has enabled download rate limits for downloads and pull requests on Docker Hub. This caps the number of objects that users can download within a specified timeframe. For more information, see [Download rate limit](download-rate-limit.md).
|
||||
|
||||
|
|
@ -199,7 +199,7 @@ Docker introduces Hub Vulnerability Scanning which enables you to automatically
|
|||
|
||||
### Enhancements
|
||||
|
||||
* The [repositories page](repos/index.md) and all
|
||||
* The [repositories page](repos/_index.md) and all
|
||||
related settings and tabs have been updated and moved from `cloud.docker.com`
|
||||
to `hub.docker.com`. You can access the page at its new URL: [https://hub.docker.com/repositories](https://hub.docker.com/repositories).
|
||||
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ weight: 50
|
|||
> [!NOTE]
|
||||
>
|
||||
> Service accounts require a
|
||||
> [Docker Team, or Business subscription](../subscription/index.md).
|
||||
> [Docker Team, or Business subscription](../subscription/_index.md).
|
||||
|
||||
A service account is a Docker ID used for automated management of container images or containerized applications. Service accounts are typically used in automated workflows, and don't share Docker IDs with the members in the organization. Common use cases for service accounts include mirroring content on Docker Hub, or tying in image pulls from your CI/CD process.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ weight: 70
|
|||
> improving your security posture, and more.
|
||||
>
|
||||
> Docker Hub static scanning requires a [Docker Pro, Team, or Business
|
||||
> subscription](../subscription/index.md).
|
||||
> subscription](../subscription/_index.md).
|
||||
|
||||
Docker Hub static vulnerability scanning lets you automatically run a
|
||||
point-in-time scan on your Docker images for vulnerabilities.
|
||||
|
|
@ -153,7 +153,7 @@ actions you can take to remediate the vulnerabilities. For example, you can:
|
|||
|
||||
Docker Scout can provide you with concrete and contextual remediation steps for
|
||||
improving image security. For more information, see
|
||||
[Docker Scout](../scout/index.md).
|
||||
[Docker Scout](../scout/_index.md).
|
||||
|
||||
### Turn off static vulnerability scanning
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ manually by a user. This makes it easier to automatically start Docker when the
|
|||
machine reboots.
|
||||
|
||||
The command to start Docker depends on your operating system. Check the correct
|
||||
page under [Install Docker](/manuals/engine/install/index.md).
|
||||
page under [Install Docker](/manuals/engine/install/_index.md).
|
||||
|
||||
### Start with systemd
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ aliases:
|
|||
> Also, static binaries may not include all functionalities provided by the dynamic
|
||||
> packages.
|
||||
>
|
||||
> On Windows and Mac, we recommend that you install [Docker Desktop](/manuals/desktop/index.md)
|
||||
> On Windows and Mac, we recommend that you install [Docker Desktop](/manuals/desktop/_index.md)
|
||||
> instead. For Linux, we recommend that you follow the instructions specific for
|
||||
> your distribution.
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ You have now successfully installed and started Docker Engine.
|
|||
> The following instructions are mostly suitable for testing purposes. The macOS
|
||||
> binary includes the Docker client only. It does not include the `dockerd` daemon
|
||||
> which is required to run containers. Therefore, we recommend that you install
|
||||
> [Docker Desktop](/manuals/desktop/index.md) instead.
|
||||
> [Docker Desktop](/manuals/desktop/_index.md) instead.
|
||||
|
||||
The binaries for Mac also do not contain:
|
||||
|
||||
|
|
@ -207,7 +207,7 @@ To install client binaries, perform the following steps:
|
|||
> Server which allows you to run Windows containers only. When you install the
|
||||
> Docker daemon on Windows Server, the daemon doesn't contain Docker components
|
||||
> such as `buildx` and `compose`. If you're running Windows 10 or 11,
|
||||
> we recommend that you install [Docker Desktop](/manuals/desktop/index.md) instead.
|
||||
> we recommend that you install [Docker Desktop](/manuals/desktop/_index.md) instead.
|
||||
|
||||
Binary packages on Windows include both `dockerd.exe` and `docker.exe`. On Windows,
|
||||
these binaries only provide the ability to run native Windows containers (not
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ manually create the group.
|
|||
>
|
||||
> The `docker` group grants root-level privileges to the user. For
|
||||
> details on how this impacts security in your system, see
|
||||
> [Docker Daemon Attack Surface](../security/index.md#docker-daemon-attack-surface).
|
||||
> [Docker Daemon Attack Surface](../security/_index.md#docker-daemon-attack-surface).
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ toc_max: 2
|
|||
> $ sudo apt-get install docker-ce docker-ce-cli containerd.io
|
||||
> ```
|
||||
>
|
||||
> See the [installation instructions](../install/index.md) for the corresponding
|
||||
> See the [installation instructions](../install/_index.md) for the corresponding
|
||||
> Linux distro for details.
|
||||
|
||||
## 18.09.9
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ toc_max: 2
|
|||
> Refer to the [Docker Engine installation instructions][1] for your operating system
|
||||
> for more details on upgrading Docker Engine.
|
||||
|
||||
[1]: ../install/index.md
|
||||
[1]: ../install/_index.md
|
||||
|
||||
This page describes the latest changes, additions, known issues, and fixes for Docker Engine version 23.0.
|
||||
|
||||
|
|
|
|||
|
|
@ -223,7 +223,7 @@ This feature provides more insight to administrators than previously available w
|
|||
the CLI for enforcing and performing image signature verification.
|
||||
|
||||
For more information on configuring Docker Content Trust Signature Verification, go to
|
||||
[Content trust in Docker](trust/index.md).
|
||||
[Content trust in Docker](trust/_index.md).
|
||||
|
||||
## Other kernel security features
|
||||
|
||||
|
|
@ -278,7 +278,7 @@ pull requests, or comments on the Docker community forums.
|
|||
|
||||
## Related information
|
||||
|
||||
* [Use trusted images](trust/index.md)
|
||||
* [Use trusted images](trust/_index.md)
|
||||
* [Seccomp security profiles for Docker](seccomp.md)
|
||||
* [AppArmor security profiles for Docker](apparmor.md)
|
||||
* [On the Security of Containers (2014)](https://medium.com/@ewindisch/on-the-security-of-containers-2c60ffe25a9e)
|
||||
|
|
|
|||
|
|
@ -97,5 +97,5 @@ If the Docker registry is accessed without a port number, do not add the port to
|
|||
|
||||
## Related information
|
||||
|
||||
* [Use trusted images](trust/index.md)
|
||||
* [Use trusted images](trust/_index.md)
|
||||
* [Protect the Docker daemon socket](protect-access.md)
|
||||
|
|
|
|||
|
|
@ -347,4 +347,4 @@ $ curl https://$HOST:2376/images/json \
|
|||
## Related information
|
||||
|
||||
* [Using certificates for repository client verification](certificates.md)
|
||||
* [Use trusted images](trust/index.md)
|
||||
* [Use trusted images](trust/_index.md)
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ keywords: trust, security, notary, deployment
|
|||
title: Deploy Notary Server with Compose
|
||||
---
|
||||
|
||||
The easiest way to deploy Notary Server is by using Docker Compose. To follow the procedure on this page, you must have already [installed Docker Compose](/manuals/compose/install/index.md).
|
||||
The easiest way to deploy Notary Server is by using Docker Compose. To follow the procedure on this page, you must have already [installed Docker Compose](/manuals/compose/install/_index.md).
|
||||
|
||||
1. Clone the Notary repository.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,9 +21,9 @@ have privileges to run docker commands on your local machine or in the VM.
|
|||
|
||||
This sandbox requires you to install two Docker tools: Docker Engine >= 1.10.0
|
||||
and Docker Compose >= 1.6.0. To install the Docker Engine, choose from the
|
||||
[list of supported platforms](../../install/index.md). To install
|
||||
[list of supported platforms](../../install/_index.md). To install
|
||||
Docker Compose, see the
|
||||
[detailed instructions here](/manuals/compose/install/index.md).
|
||||
[detailed instructions here](/manuals/compose/install/_index.md).
|
||||
|
||||
## What is in the sandbox?
|
||||
|
||||
|
|
|
|||
|
|
@ -128,7 +128,7 @@ roll back to a previous version of the service.
|
|||
## What's next?
|
||||
|
||||
* Learn Swarm mode [key concepts](key-concepts.md).
|
||||
* Get started with the [Swarm mode tutorial](swarm-tutorial/index.md).
|
||||
* Get started with the [Swarm mode tutorial](swarm-tutorial/_index.md).
|
||||
* Explore Swarm mode CLI commands
|
||||
* [swarm init](/reference/cli/docker/swarm/init.md)
|
||||
* [swarm join](/reference/cli/docker/swarm/join.md)
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ There are two types of nodes: [managers](#manager-nodes) and
|
|||
|
||||
|
||||
If you haven't already, read through the
|
||||
[Swarm mode overview](../index.md) and
|
||||
[Swarm mode overview](../_index.md) and
|
||||
[key concepts](../key-concepts.md).
|
||||
|
||||
## Manager nodes
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ ports open between the swarm nodes before you enable Swarm mode:
|
|||
* Port `4789` UDP (configurable) for the container ingress network.
|
||||
|
||||
When setting up networking in a Swarm, special care should be taken. Consult
|
||||
the [tutorial](swarm-tutorial/index.md#open-protocols-and-ports-between-the-hosts)
|
||||
the [tutorial](swarm-tutorial/_index.md#open-protocols-and-ports-between-the-hosts)
|
||||
for an overview.
|
||||
|
||||
You must also open the published port between the swarm nodes and any external
|
||||
|
|
|
|||
|
|
@ -99,4 +99,4 @@ This node joined a swarm as a manager.
|
|||
## Learn More
|
||||
|
||||
* `swarm join` [command line reference](/reference/cli/docker/swarm/join.md)
|
||||
* [Swarm mode tutorial](swarm-tutorial/index.md)
|
||||
* [Swarm mode tutorial](swarm-tutorial/_index.md)
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ that only swarm managers can manage a swarm, while standalone containers can be
|
|||
started on any daemon. Docker daemons can participate in a swarm as managers,
|
||||
workers, or both.
|
||||
|
||||
In the same way that you can use [Docker Compose](/manuals/compose/index.md) to define and run
|
||||
In the same way that you can use [Docker Compose](/manuals/compose/_index.md) to define and run
|
||||
containers, you can define and run [Swarm service](services.md) stacks.
|
||||
|
||||
Keep reading for details about concepts related to Docker swarm services,
|
||||
|
|
@ -108,4 +108,4 @@ the service.
|
|||
## What's next?
|
||||
|
||||
* Read the [Swarm mode overview](index.md).
|
||||
* Get started with the [Swarm mode tutorial](swarm-tutorial/index.md).
|
||||
* Get started with the [Swarm mode tutorial](swarm-tutorial/_index.md).
|
||||
|
|
|
|||
|
|
@ -242,4 +242,4 @@ $ docker node rm node-2
|
|||
|
||||
* [Swarm administration guide](admin_guide.md)
|
||||
* [Docker Engine command line reference](/reference/cli/docker/)
|
||||
* [Swarm mode tutorial](swarm-tutorial/index.md)
|
||||
* [Swarm mode tutorial](swarm-tutorial/_index.md)
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ each other over the following ports:
|
|||
* Port `4789` UDP (configurable) for the overlay network (including ingress) data path.
|
||||
|
||||
When setting up networking in a Swarm, special care should be taken. Consult
|
||||
the [tutorial](swarm-tutorial/index.md#open-protocols-and-ports-between-the-hosts)
|
||||
the [tutorial](swarm-tutorial/_index.md#open-protocols-and-ports-between-the-hosts)
|
||||
for an overview.
|
||||
|
||||
## Overlay networking
|
||||
|
|
@ -477,6 +477,6 @@ preferred because it is somewhat self-documenting.
|
|||
|
||||
* [Deploy services to a swarm](services.md)
|
||||
* [Swarm administration guide](admin_guide.md)
|
||||
* [Swarm mode tutorial](swarm-tutorial/index.md)
|
||||
* [Swarm mode tutorial](swarm-tutorial/_index.md)
|
||||
* [Networking overview](/manuals/engine/network/_index.md)
|
||||
* [Docker CLI reference](/reference/cli/docker/)
|
||||
|
|
|
|||
|
|
@ -259,7 +259,7 @@ different ways, depending on your desired outcome.
|
|||
An image version can be expressed in several different ways:
|
||||
|
||||
- If you specify a tag, the manager (or the Docker client, if you use
|
||||
[content trust](../security/trust/index.md)) resolves that tag to a digest.
|
||||
[content trust](../security/trust/_index.md)) resolves that tag to a digest.
|
||||
When the request to create a container task is received on a worker node, the
|
||||
worker node only sees the digest, not the tag.
|
||||
|
||||
|
|
@ -306,7 +306,7 @@ of the image.
|
|||
|
||||
> [!NOTE]>
|
||||
>
|
||||
> If [content trust](../security/trust/index.md) is
|
||||
> If [content trust](../security/trust/_index.md) is
|
||||
> enabled, the client actually resolves the image's tag to a digest before
|
||||
> contacting the swarm manager, to verify that the image is signed.
|
||||
> Thus, if you use content trust, the swarm manager receives the request
|
||||
|
|
@ -358,7 +358,7 @@ points to and updates the service tasks to use that digest.
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> If you use [content trust](../security/trust/index.md), the Docker
|
||||
> If you use [content trust](../security/trust/_index.md), the Docker
|
||||
> client resolves image and the swarm manager receives the image and digest,
|
||||
> rather than a tag.
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ To run through this tutorial, you need:
|
|||
> `docker stack` and `docker service` commands must be run from a manager
|
||||
> node.
|
||||
|
||||
2. A current version of [Docker Compose](/manuals/compose/install/index.md).
|
||||
2. A current version of [Docker Compose](/manuals/compose/install/_index.md).
|
||||
|
||||
## Set up a Docker registry
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ These instructions assume you have installed the Docker Engine on
|
|||
a machine to serve as a manager node in your swarm.
|
||||
|
||||
If you haven't already, read through the [Swarm mode key concepts](key-concepts.md)
|
||||
and try the [Swarm mode tutorial](swarm-tutorial/index.md).
|
||||
and try the [Swarm mode tutorial](swarm-tutorial/_index.md).
|
||||
|
||||
## Create a swarm
|
||||
|
||||
|
|
@ -215,4 +215,4 @@ To add a worker to this swarm, run the following command:
|
|||
|
||||
* [Join nodes to a swarm](join-nodes.md)
|
||||
* `swarm init` [command line reference](/reference/cli/docker/swarm/init.md)
|
||||
* [Swarm mode tutorial](swarm-tutorial/index.md)
|
||||
* [Swarm mode tutorial](swarm-tutorial/_index.md)
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ The tutorial guides you through:
|
|||
This tutorial uses Docker Engine CLI commands entered on the command line of a
|
||||
terminal window.
|
||||
|
||||
If you are brand new to Docker, see [About Docker Engine](../../index.md).
|
||||
If you are brand new to Docker, see [About Docker Engine](../../_index.md).
|
||||
|
||||
## Set up
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ workers (`worker1` and `worker2`).
|
|||
#### Install Docker Engine on Linux machines
|
||||
|
||||
If you are using Linux based physical computers or cloud-provided computers as
|
||||
hosts, simply follow the [Linux install instructions](../../install/index.md)
|
||||
hosts, simply follow the [Linux install instructions](../../install/_index.md)
|
||||
for your platform. Spin up the three machines, and you are ready. You can test both
|
||||
single-node and multi-node swarm scenarios on Linux machines.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ aliases:
|
|||
|
||||
Docker Extensions let you use third-party tools within Docker Desktop to extend its functionality.
|
||||
|
||||
You can seamlessly connect your favorite development tools to your application development and deployment workflows. Augment Docker Desktop with debugging, testing, security, and networking functionalities, and create custom add-ons using the Extensions [SDK](extensions-sdk/index.md).
|
||||
You can seamlessly connect your favorite development tools to your application development and deployment workflows. Augment Docker Desktop with debugging, testing, security, and networking functionalities, and create custom add-ons using the Extensions [SDK](extensions-sdk/_index.md).
|
||||
|
||||
Anyone can use Docker Extensions and there is no limit to the number of extensions you can install.
|
||||
|
||||
|
|
|
|||
|
|
@ -42,7 +42,7 @@ At the root of the image filesystem is a `metadata.json` file which describes th
|
|||
It's a fundamental element of a Docker extension.
|
||||
|
||||
An extension can contain a UI part and backend parts that run either on the host or in the Desktop virtual machine.
|
||||
For further information, see [Architecture](architecture/index.md).
|
||||
For further information, see [Architecture](architecture/_index.md).
|
||||
|
||||
You distribute extensions through Docker Hub. However, you can develop them locally without the need to push
|
||||
the extension to Docker Hub. See [Extensions distribution](extensions/DISTRIBUTION.md) for further details.
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ builders have used the backend to:
|
|||
- Store data in a local database and serve them back with a REST API.
|
||||
- Store the extension state, for example when a button starts a long-running process, so that if you navigate away from the extension user interface and comes back, the frontend can pick up where it left off.
|
||||
|
||||
For more information about extension backends, see [Architecture](../architecture/index.md#the-backend).
|
||||
For more information about extension backends, see [Architecture](../architecture/_index.md#the-backend).
|
||||
|
||||
## Add a backend to the extension
|
||||
|
||||
|
|
@ -357,5 +357,5 @@ call displayed.
|
|||
|
||||
## What's next?
|
||||
|
||||
- Learn how to [share and publish your extension](../extensions/index.md).
|
||||
- Learn more about extensions [architecture](../architecture/index.md).
|
||||
- Learn how to [share and publish your extension](../extensions/_index.md).
|
||||
- Learn more about extensions [architecture](../architecture/_index.md).
|
||||
|
|
|
|||
|
|
@ -352,6 +352,6 @@ when you need to debug it.
|
|||
- Add a [backend](backend-extension-tutorial.md) to your extension.
|
||||
- Learn how to [test and debug](../dev/test-debug.md) your extension.
|
||||
- Learn how to [setup CI for your extension](../dev/continuous-integration.md).
|
||||
- Learn more about extensions [architecture](../architecture/index.md).
|
||||
- Learn more about extensions [architecture](../architecture/_index.md).
|
||||
- For more information and guidelines on building the UI, see the [Design and UI styling section](../design/design-guidelines.md).
|
||||
- If you want to set up user authentication for the extension, see [Authentication](../guides/oauth2-flow.md).
|
||||
|
|
|
|||
|
|
@ -105,4 +105,4 @@ The left-hand menu displays a new tab with the name of your extension.
|
|||
- Build a more [advanced frontend](frontend-extension-tutorial.md) extension.
|
||||
- Learn how to [test and debug](../dev/test-debug.md) your extension.
|
||||
- Learn how to [setup CI for your extension](../dev/continuous-integration.md).
|
||||
- Learn more about extensions [architecture](../architecture/index.md).
|
||||
- Learn more about extensions [architecture](../architecture/_index.md).
|
||||
|
|
|
|||
|
|
@ -50,4 +50,4 @@ Our colors have been chosen so that the counterpart colors in each variant of th
|
|||
## What's next?
|
||||
|
||||
- Take a look at our [MUI best practices](mui-best-practices.md).
|
||||
- Learn how to [publish your extension](../extensions/index.md).
|
||||
- Learn how to [publish your extension](../extensions/_index.md).
|
||||
|
|
|
|||
|
|
@ -70,4 +70,4 @@ When creating your extension, ensure that first time users of the extension and
|
|||
|
||||
- Explore our [design principles](design-principles.md).
|
||||
- Take a look at our [UI styling guidelines](index.md).
|
||||
- Learn how to [publish your extension](../extensions/index.md).
|
||||
- Learn how to [publish your extension](../extensions/_index.md).
|
||||
|
|
|
|||
|
|
@ -29,4 +29,4 @@ Our products focus on inclusive growth and are continuously useful and adapt to
|
|||
## What's next?
|
||||
|
||||
- Take a look at our [UI styling guidelines](index.md).
|
||||
- Learn how to [publish your extension](../extensions/index.md).
|
||||
- Learn how to [publish your extension](../extensions/_index.md).
|
||||
|
|
|
|||
|
|
@ -49,4 +49,4 @@ Some of the above options require you to extend our MUI theme. See the MUI docum
|
|||
## What's next?
|
||||
|
||||
- Take a look at our [UI styling guide](index.md).
|
||||
- Learn how to [publish your extension](../extensions/index.md).
|
||||
- Learn how to [publish your extension](../extensions/_index.md).
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Here is the list of labels you can or need to specify when building your extensi
|
|||
>
|
||||
> Docker Desktop applies CSS styles to the provided HTML content. You can make sure that it renders correctly
|
||||
> [within the Marketplace](#preview-the-extension-in-the-marketplace). It is recommended that you follow the
|
||||
> [styling guidelines](../design/index.md).
|
||||
> [styling guidelines](../design/_index.md).
|
||||
|
||||
## Preview the extension in the Marketplace
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ extension. If you request a review from the Docker Extensions team and have not
|
|||
|
||||
These guidelines don't replace Docker's terms of service or guarantee approval:
|
||||
- Review the [design guidelines](../design/design-guidelines.md)
|
||||
- Ensure the [UI styling](../design/index.md) is in line with Docker Desktop guidelines
|
||||
- Ensure the [UI styling](../design/_index.md) is in line with Docker Desktop guidelines
|
||||
- Ensure your extensions support both light and dark mode
|
||||
- Consider the needs of both new and existing users of your extension
|
||||
- Test your extension with potential users
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ However host binaries invoke from the extension executables (as binaries, shell
|
|||
shipped as part of your extension and deployed to the host. As extensions can run on multiple platforms, this
|
||||
means that you need to ship the executables for all the platforms you want to support.
|
||||
|
||||
Learn more about extensions [architecture](../architecture/index.md).
|
||||
Learn more about extensions [architecture](../architecture/_index.md).
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
|
|
|
|||
|
|
@ -93,4 +93,4 @@ It's highly recommended that you use an external source of storage to store the
|
|||
|
||||
## What's next
|
||||
|
||||
Learn how to [publish and distribute your extension](../extensions/index.md)
|
||||
Learn how to [publish and distribute your extension](../extensions/_index.md)
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ For further inspiration, see the other examples in the [samples folder](https://
|
|||
|
||||
> [!TIP]
|
||||
>
|
||||
> Whilst creating your extension, make sure you follow the [design](design/design-guidelines.md) and [UI styling](design/index.md) guidelines to ensure visual consistency and [level AA accessibility standards](https://www.w3.org/WAI/WCAG2AA-Conformance).
|
||||
> Whilst creating your extension, make sure you follow the [design](design/design-guidelines.md) and [UI styling](design/_index.md) guidelines to ensure visual consistency and [level AA accessibility standards](https://www.w3.org/WAI/WCAG2AA-Conformance).
|
||||
|
||||
## Part two: Publish and distribute your extension
|
||||
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ hidden from the Docker Dashboard. You can change this in **Settings**, see
|
|||
|
||||
## Step four: Submit and publish your extension to the Marketplace
|
||||
|
||||
If you want to make your extension available to all Docker Desktop users, you can submit it for publication in the Marketplace. For more information, see [Publish](extensions/index.md).
|
||||
If you want to make your extension available to all Docker Desktop users, you can submit it for publication in the Marketplace. For more information, see [Publish](extensions/_index.md).
|
||||
|
||||
## Clean up
|
||||
|
||||
|
|
@ -91,5 +91,5 @@ $ docker extension rm <name-of-your-extension>
|
|||
- Build a more [advanced frontend](build/frontend-extension-tutorial.md) for your extension.
|
||||
- Learn how to [test and debug](dev/test-debug.md) your extension.
|
||||
- Learn how to [setup CI for your extension](dev/continuous-integration.md).
|
||||
- Learn more about extensions [architecture](architecture/index.md).
|
||||
- Learn more about extensions [architecture](architecture/_index.md).
|
||||
- Learn more about [designing the UI](design/design-guidelines.md).
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ Docker Extensions is switched on by default. To change your settings:
|
|||
> - `~/Library/Group Containers/group.com.docker/settings.json` on Mac
|
||||
> - `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings.json` on Windows
|
||||
>
|
||||
> This can also be done with [Hardened Docker Desktop](/manuals/security/for-admins/hardened-desktop/index.md)
|
||||
> This can also be done with [Hardened Docker Desktop](/manuals/security/for-admins/hardened-desktop/_index.md)
|
||||
|
||||
### Turn on or turn off extensions not available in the Marketplace
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ The following environment monitoring integrations are available
|
|||
- [Sysdig](./environment/sysdig.md)
|
||||
|
||||
For more information about environment integrations, see
|
||||
[Environments](./environment/index.md).
|
||||
[Environments](./environment/_index.md).
|
||||
|
||||
### Code quality
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ These techniques include:
|
|||
|
||||
When Enhanced Container Isolation is enabled, these mechanisms are applied automatically and with minimal functional or performance impact to developers. Developers continue to use Docker Desktop as usual, but the containers they launch are more strongly isolated.
|
||||
|
||||
Enhanced Container Isolation ensures stronger container isolation and also locks in any security configurations that have been created by IT admins, for instance through [Registry Access Management policies](/manuals/security/for-admins/hardened-desktop/registry-access-management.md) or with [Settings Management](../settings-management/index.md).
|
||||
Enhanced Container Isolation ensures stronger container isolation and also locks in any security configurations that have been created by IT admins, for instance through [Registry Access Management policies](/manuals/security/for-admins/hardened-desktop/registry-access-management.md) or with [Settings Management](../settings-management/_index.md).
|
||||
|
||||
> [!NOTE]
|
||||
>
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ Note however that ECI on WSL is not as secure as on Hyper-V because:
|
|||
and use that access to modify Docker Engine settings inside the VM. This gives
|
||||
Docker Desktop users control of the Docker Desktop VM and allows them to
|
||||
bypass Docker Desktop configs set by admins via the
|
||||
[settings-management](../settings-management/index.md) feature. In contrast,
|
||||
[settings-management](../settings-management/_index.md) feature. In contrast,
|
||||
ECI on Hyper-V does not allow Docker Desktop users to breach the Docker
|
||||
Desktop Linux VM.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ aliases:
|
|||
|
||||
Settings Management is a feature that helps admins to control certain Docker Desktop settings on client machines within their organization.
|
||||
|
||||
With a few lines of JSON, admins can configure controls for Docker Desktop settings such as proxies and network settings. For an extra layer of security, admins can also use Settings Management to enable and lock in [Enhanced Container Isolation](../enhanced-container-isolation/index.md) which ensures that any configurations set with Settings Management cannot be modified by containers.
|
||||
With a few lines of JSON, admins can configure controls for Docker Desktop settings such as proxies and network settings. For an extra layer of security, admins can also use Settings Management to enable and lock in [Enhanced Container Isolation](../enhanced-container-isolation/_index.md) which ensures that any configurations set with Settings Management cannot be modified by containers.
|
||||
|
||||
It is available with [Docker Desktop 4.13.0 and later](/manuals/desktop/release-notes.md).
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ Values that are set to `locked: true` within the `admin-settings.json` override
|
|||
|
||||
Using the `admin-settings.json` file, admins can:
|
||||
|
||||
- Turn on and lock in [Enhanced Container Isolation](../enhanced-container-isolation/index.md)
|
||||
- Turn on and lock in [Enhanced Container Isolation](../enhanced-container-isolation/_index.md)
|
||||
- Configure HTTP proxies
|
||||
- Configure network settings
|
||||
- Configure Kubernetes settings
|
||||
|
|
|
|||
|
|
@ -195,7 +195,7 @@ The following `admin-settings.json` code and table provides an example of the re
|
|||
| `windowsDockerdPort` | Windows only | Exposes Docker Desktop's internal proxy locally on this port for the Windows Docker daemon to connect to. If it is set to 0, a random free port is chosen. If the value is greater than 0, use that exact value for the port. The default value is -1 which disables the option. Note: This is available for Windows containers only. |
|
||||
| `enableKerberosNtlm` | |When set to `true`, Kerberos and NTLM authentication is enabled. Default is `false`. Available in Docker Desktop version 4.32 and later. For more information, see the settings documentation. |
|
||||
| `containersProxy` (Beta) | | Allows you to create air-gapped containers. For more information see [Air-Gapped Containers](../air-gapped-containers.md).|
|
||||
| `enhancedContainerIsolation` | | If `value` is set to true, Docker Desktop runs all containers as unprivileged, via the Linux user-namespace, prevents them from modifying sensitive configurations inside the Docker Desktop VM, and uses other advanced techniques to isolate them. For more information, see [Enhanced Container Isolation](../enhanced-container-isolation/index.md).|
|
||||
| `enhancedContainerIsolation` | | If `value` is set to true, Docker Desktop runs all containers as unprivileged, via the Linux user-namespace, prevents them from modifying sensitive configurations inside the Docker Desktop VM, and uses other advanced techniques to isolate them. For more information, see [Enhanced Container Isolation](../enhanced-container-isolation/_index.md).|
|
||||
| `dockerSocketMount` | | By default, enhanced container isolation blocks bind-mounting the Docker Engine socket into containers (e.g., `docker run -v /var/run/docker.sock:/var/run/docker.sock ...`). This allows admins to relax this in a controlled way. See [ECI Configuration](../enhanced-container-isolation/config.md) for more info. |
|
||||
| `imageList` | | Indicates which container images are allowed to bind-mount the Docker Engine socket. |
|
||||
| `commandList` | | Restricts the commands that containers can issue via the bind-mounted Docker Engine socket. |
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ When prompted for a password, enter your personal access token instead of a pass
|
|||
|
||||
> [!NOTE]
|
||||
>
|
||||
> If you have [two-factor authentication (2FA)](2fa/index.md) enabled, you must
|
||||
> If you have [two-factor authentication (2FA)](2fa/_index.md) enabled, you must
|
||||
> use a personal access token when logging in from the Docker CLI. 2FA is an
|
||||
> optional, but more secure method of authentication.
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Docker Pro includes:
|
|||
- All the features available in Personal
|
||||
- Unlimited private repositories
|
||||
- 5000 image [pulls per day](../../docker-hub/download-rate-limit.md)
|
||||
- [Auto Builds](../../docker-hub/builds/index.md) with 5 concurrent builds
|
||||
- [Auto Builds](../../docker-hub/builds/_index.md) with 5 concurrent builds
|
||||
- 300 [Vulnerability Scans](../../docker-hub/vulnerability-scanning.md)
|
||||
|
||||
For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/).
|
||||
|
|
@ -52,7 +52,7 @@ For a list of features available in each tier, see [Docker Pricing](https://www.
|
|||
Docker Team includes:
|
||||
- Everything included in Docker Pro
|
||||
- Unlimited teams
|
||||
- [Auto Builds](../../docker-hub/builds/index.md) with 15 concurrent builds
|
||||
- [Auto Builds](../../docker-hub/builds/_index.md) with 15 concurrent builds
|
||||
- Unlimited [Vulnerability Scanning](../../docker-hub/vulnerability-scanning.md)
|
||||
- 5000 image [pulls per day](../../docker-hub/download-rate-limit.md) for each team member
|
||||
|
||||
|
|
@ -66,11 +66,11 @@ For a list of features available in each tier, see [Docker Pricing](https://www.
|
|||
|
||||
Docker Business includes:
|
||||
- Everything included in Docker Team
|
||||
- [Hardened Docker Desktop](/manuals/security/for-admins/hardened-desktop/index.md)
|
||||
- [Hardened Docker Desktop](/manuals/security/for-admins/hardened-desktop/_index.md)
|
||||
- [Image Access Management](/manuals/security/for-admins/hardened-desktop/image-access-management.md) which lets admins control what content developers can access
|
||||
- [Registry Access Management](/manuals/security/for-admins/hardened-desktop/registry-access-management.md) which lets admins control what registries developers can access
|
||||
- [Company layer](../../admin/company/_index.md) to manage multiple organizations and settings
|
||||
- [Single Sign-On](../../security/for-admins/single-sign-on/index.md)
|
||||
- [Single Sign-On](../../security/for-admins/single-sign-on/_index.md)
|
||||
- [System for Cross-domain Identity Management](../../security/for-admins/provisioning/scim.md) and more.
|
||||
|
||||
For a list of features available in each tier, see [Docker Pricing](https://www.docker.com/pricing/).
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue