Remove Desktop Enterprise docs

Signed-off-by: Usha Mandya <usha.mandya@docker.com>

_data/toc.yaml

@@ -1465,37 +1465,3 @@ manuals:
     - path: /toolbox/faqs/troubleshoot/
       title: Troubleshooting
       nosync: true
-- sectiontitle: Docker Desktop Enterprise
-  section:
-  - path: /desktop/enterprise/
-    title: Overview
-  - path: /desktop/enterprise/release-notes/
-    title: Release notes
-  - sectiontitle: Admin
-    section:
-    - sectiontitle: Install
-      section:
-      - path: /desktop/enterprise/admin/install/mac/
-        title: Install DDE on Mac
-      - path: /desktop/enterprise/admin/install/windows/
-        title: Install DDE on Windows
-    - sectiontitle: Configure
-      section:
-      - path: /desktop/enterprise/admin/configure/mac-admin/
-        title: Configure DDE on Mac
-      - path: /desktop/enterprise/admin/configure/windows-admin/
-        title: Configure DDE on Windows
-  - sectiontitle: User
-    section:
-    - path: /desktop/enterprise/user/mac-user/
-      title: Use DDE on Mac
-    - path: /desktop/enterprise/user/windows-user/
-      title: Use DDE on Windows
-  - path: /desktop/enterprise/app-designer/
-    title: Application designer
-  - sectiontitle: Troubleshoot
-    section:
-    - path: /desktop/enterprise/troubleshoot/mac-issues/
-      title: Troubleshoot DDE issues on Mac
-    - path: /desktop/enterprise/troubleshoot/windows-issues/
-      title: Troubleshoot DDE issues on Windows

desktop/enterprise/admin/configure/mac-admin.md

@@ -1,202 +0,0 @@
----
-title: Configure Docker Desktop Enterprise on Mac
-description: Learn about Docker Desktop Enterprise
-keywords: Docker EE, Windows, Mac, Docker Desktop, Enterprise
-redirect_from:
-- /ee/desktop/admin/configure/mac-admin/
----
-
-This page contains information on how system administrators can configure Docker Desktop Enterprise (DDE) settings, specify and lock configuration parameters to create a standardized development environment on Mac operating systems.
-
-## Environment configuration (administrators only)
-
-The administrator configuration file allows you to customize and standardize your Docker Desktop environment across the organization.
-
-When you install Docker Desktop Enterprise, a configuration file with default values is installed at the following location. Do not change the location of the `admin-settings.json` file.
-
-`/Library/Application Support/Docker/DockerDesktop/admin-settings.json`
-
-To edit `admin-settings.json`, you must have sudo access privileges.
-
-### Syntax for `admin-settings.json`
-
-1. `configurationFileVersion`: This must be the first parameter listed in `admin-settings.json`. It specifies the version of the configuration file format and must not be changed.
-
-2. A nested list of configuration parameters, each of which contains a minimum of the following two settings:
-
-  - `locked`: If set to `true`, users without elevated access privileges are not able to edit this setting from the UI or by directly editing the `settings.json` file (the `settings.json` file stores the user's preferences). If set to `false`, users without elevated access privileges can change this setting from the UI or by directly editing
-  `settings.json`. If this setting is omitted, the default value is `false`.
-
-  - `value`: Specifies the value of the parameter. Docker Desktop Enterprise uses the value when first started and after a reset to factory defaults. If this setting is omitted, a default value that is built into the application is used.
-
-### Parameters and settings
-
-The following `admin-settings.json` code and table provide the required syntax and descriptions for parameters and values:
-
-```json
-{
-  "configurationFileVersion": 2,
-  "analyticsEnabled": {
-    "locked": false,
-    "value": false
-  },
-  "dockerCliOptions": {
-    "stackOrchestrator": {
-      "locked": false,
-      "value": "swarm"
-    }
-  },
-  "proxy": {
-    "locked": false,
-    "value": {
-      "http": "http://proxy.docker.com:8080",
-      "https": "https://proxy.docker.com:8080",
-      "exclude": "docker.com,github.com"
-    }
-  },
-  "linuxVM": {
-    "cpus": {
-      "locked": false,
-      "value": 2
-    },
-    "memoryMiB": {
-      "locked": false,
-      "value": 2048
-    },
-    "swapMiB": {
-      "locked": false,
-      "value": 1024
-    },
-    "dataFolder": {
-      "locked": false,
-      "value": "/Users/..."
-    },
-    "diskSizeMiB": {
-      "locked": false,
-      "value": 65536
-    },
-    "dockerDaemonOptions": {
-      "experimental": {
-        "locked": false,
-        "value": true
-      }
-    }
-  },
-  "kubernetes": {
-    "enabled": {
-      "locked": false,
-      "value": false
-    },
-    "showSystemContainers": {
-      "locked": false,
-      "value": false
-    },
-    "podNetworkCIDR": {
-      "locked": false,
-      "value": null
-    },
-    "serviceCIDR": {
-      "locked": false,
-      "value": null
-    }
-  },
-  "template": {
-    "defaultOrg": {
-      "value": "myorg",
-      "locked": true
-    },
-    "defaultRegistry": {
-      "value": "mydtr:5000",
-      "locked": true
-    },
-    "repositories": {
-      "value": [
-        "https://one/library.yaml",
-        "https://two/library.yaml",
-        "https://three/library.yaml"
-      ],
-      "locked": true
-    }
-  },
-  "filesharingDirectories": {
-    "locked": false,
-    "value": [
-      "/Users"
-    ]
-  }
-}
-```
-
-Parameter values and descriptions for environment configuration on Mac:
-
-| Parameter                        | Description                      |
-| :--------------------------------- | :--------------------------------- |
-| `configurationFileVersion`        | Specifies the version of the configuration file format.    |
-| `analyticsEnabled`                | If `value` is true, allow Docker Desktop Enterprise to sends diagnostics, crash reports, and usage data. This information helps Docker improve and troubleshoot the application.                |
-| `dockerCliOptions`                | Specifies key-value pairs in the user's `~/.docker/config.json` file. In the sample code provided, the orchestration for docker stack commands is set to `swarm` rather than `kubernetes`. |
-| `proxy`                          | The `http` setting specifies the HTTP proxy setting. The `https` setting specifies the HTTPS proxy setting. The `exclude` setting specifies a comma-separated list of hosts and domains to bypass the proxy. **Warning:** This parameter should be locked after being set: `locked: "true"`.                 |
-| `linuxVM`                         | Parameters and settings related to the Linux VM - grouped together in this example for convenience.          |
-| `cpus`                            | Specifies the default number of virtual CPUs for the VM. If the physical machine has only 1 core, the default value is set to 1.    |
-| `memoryMiB`                       | Specifies the amount of memory in MiB (1 MiB = 1048576 bytes) allocated for the VM.|
-| `swapMiB`                         | Specifies the amount of memory in MiB (1 MiB = 1048576 bytes) allocated for the swap file.                |
-| `dataFolder`                      | Specifies the directory containing the VM disk files.  |
-| `diskSizeMiB`                     | Specifies the amount of disk storage in MiB (1 MiB = 1048576 bytes) allocated for images and containers.                       |
-| `dockerDaemonOptions`             | Overrides the options in the linux daemon config file. For more information, see [Docker engine reference](/engine/reference/commandline/dockerd/#daemon-configuration-file).        |
-| (End of `linuxVM` section.)       |                                   |
-| `kubernetes`                      | Parameters and settings related to kubernetes options - grouped together here for convenience.                  |
-| `enabled`                         | If `locked` is set to `true`, the Kubernetes cluster starts when Docker Desktop Enterprise is  started.                          |
-| `showSystemContainers`            | If true, displays Kubernetes internal containers when running docker commands such as `docker ps`.     |
-| `podNetworkCIDR`                  | This is currently unimplemented. `locked` must be set to true.     |
-| `serviceCIDR`                     | This is currently unimplemented. `locked` must be set to true.     |
-| (End of `kubernetes` section.)    |                                   |
-|`template`|Parameters and settings related to Docker Template and Application Designer - grouped together in this example for convenience. |
-|`defaultOrg`| Specifies the default organization to be used in Docker Template and Docker Application Designer. If `locked` is set to `true`, the Kubernetes cluster starts when Docker Desktop Enterprise is started. |
-|`defaultRegistry`|Specifies the default registry to be used in Docker Template and Application Designer.|
-|`repositories`|Lists the repositories that are allowed.|
-| `filesharingDirectories`          | The host folders that users can bind-mount in containers.         |
-=======
-
-### File format update
-
-#### From version 1 to 2
-
-Docker Desktop Enterprise 2.3.0.0-ent contains a change in the configuration file format.
-
-If you haven’t made any changes to the `admin-settings.json` file in the previous installation, you can simply delete it and Docker Desktop will re-create it automatically.
-Otherwise manual steps are required to update the `admin-settings.json` file.
-
-1. Increase the value of the `configurationFileVersion` field from `1` to `2`, i.e. before:
-    ```json
-   {
-      "configurationFileVersion": 1,
-      ...
-   }
-    ```
-    after:
-    ```json
-   {
-      "configurationFileVersion": 2,
-      ...
-   }
-    ```
-
-2. Move the `filesharingDirectories` field outside the `linuxVM` field, e.g. before:
-    ```json
-      "linuxVM": {
-        ...
-        "filesharingDirectories": {
-          "locked": true,
-          "value": ["/Users"]
-        }
-      }
-    ```
-    after:
-    ```json
-      "linuxVM": {
-        ...
-      },
-      "filesharingDirectories": {
-        "locked": true,
-        "value": ["/Users"]
-      }
-    ```

desktop/enterprise/admin/configure/windows-admin.md

@@ -1,250 +0,0 @@
----
-title: Configure Docker Desktop Enterprise on Windows
-description: Learn about Docker Desktop Enterprise configuration
-keywords: Docker Admin, Windows, Docker Desktop, Enterprise
-redirect_from:
-- /ee/desktop/admin/configure/windows-admin/
----
-
-This page contains information on how system administrators can configure Docker Desktop Enterprise (DDE) settings, specify and lock configuration parameters to create a standardized development environment on Windows operating systems.
-
-## Environment configuration (administrators only)
-
-The administrator configuration file allows you to customize and standardize your Docker Desktop environment across the organization.
-
-When you install Docker Desktop Enterprise, a configuration file with default values is installed at the following location. Do not change the location of the `admin-settings.json` file.
-
-`%ProgramData%\DockerDesktop\admin-settings.json`
-
-which defaults to:
-
-`C:\ProgramData\DockerDesktop\admin-settings.json`
-
-You must have administrator access privileges to edit `admin-settings.json`.
-
-### Syntax for `admin-settings.json`
-
-1. `configurationFileVersion`: This must be the first parameter listed in `admin-settings.json`. It specifies the version of the configuration file format and must not be changed.
-
-2. A nested list of configuration parameters, each of which contains a minimum of
-    the following two settings:
-
-- `locked`: If set to `true`, users without elevated access privileges are not able to edit this setting
-    from the UI or by directly editing the `settings.json` file (the `settings.json` file stores the user's preferences). If set to `false`, users without elevated access privileges can change this setting from the UI or by directly editing
-    `settings.json`. If this setting is omitted, the default value is `false'.
-
-- `value`: Specifies the value of the parameter. Docker Desktop Enterprise uses the value when first started and after a reset to factory defaults. If this setting is omitted, a default value that is built into the application is used.
-
-### Parameters and settings
-
-The following `admin-settings.json` code and table provide the required syntax and descriptions for parameters and values:
-
-```json
-{
-  "configurationFileVersion": 2,
-  "engine": {
-    "locked": false,
-    "value": "linux"
-  },
-  "analyticsEnabled": {
-    "locked": false,
-    "value": false
-  },
-  "exposeDockerAPIOnTCP2375": {
-    "locked": false,
-    "value": false
-  },
-  "dockerCliOptions": {
-    "stackOrchestrator": {
-      "locked": false,
-      "value": "swarm"
-    }
-  },
-  "proxy": {
-    "locked": false,
-    "value": {
-      "http": "http://proxy.docker.com:8080",
-      "https": "https://proxy.docker.com:8080",
-      "exclude": "docker.com,github.com"
-    }
-  },
-  "linuxVM": {
-    "cpus": {
-      "locked": false,
-      "value": 2
-    },
-    "memoryMiB": {
-      "locked": false,
-      "value": 2048
-    },
-    "swapMiB": {
-      "locked": false,
-      "value": 1024
-    },
-    "dataFolder": {
-      "locked": false,
-      "value": null
-    },
-    "diskSizeMiB": {
-      "locked": false,
-      "value": 65536
-    },
-    "hypervCIDR": {
-      "locked": false,
-      "value": "10.0.75.0/28"
-    },
-    "vpnkitCIDR": {
-      "locked": false,
-      "value": "192.168.65.0/28"
-    },
-    "useDnsForwarder": {
-      "locked": false,
-      "value": true
-    },
-    "dns": {
-      "locked": false,
-      "value": "8.8.8.8"
-    },
-    "dockerDaemonOptions": {
-      "experimental": {
-        "locked": false,
-        "value": true
-      }
-    }
-  },
-  "windows": {
-    "dockerDaemonOptions": {
-      "experimental": {
-        "locked": false,
-        "value": true
-      }
-    }
-  },
-  "kubernetes": {
-    "enabled": {
-      "locked": false,
-      "value": false
-    },
-    "showSystemContainers": {
-      "locked": false,
-      "value": false
-    },
-    "podNetworkCIDR": {
-      "locked": false,
-      "value": null
-    },
-    "serviceCIDR": {
-      "locked": false,
-      "value": null
-    }
-  },
-  "template": {
-    "defaultOrg": {
-      "value": "myorg",
-      "locked": true
-    },
-    "defaultRegistry": {
-      "value": "mydtr:5000",
-      "locked": true
-    },
-    "repositories": {
-      "value": [
-        "https://one/library.yaml",
-        "https://two/library.yaml",
-        "https://three/library.yaml"
-      ],
-      "locked": true
-    }
-  },
-  "filesharingDirectories": {
-    "locked": false,
-    "value": [
-      "%USERPROFILE%"
-    ]
-  }
-}
-```
-
-Parameter values and descriptions for environment configuration on Windows:
-
-| Parameter                        | Description                      |
-| :--------------------------------- | :--------------------------------- |
-| `configurationFileVersion`        | Specifies the version of the configuration file format.    |
-| `engine`                          | Specifies the default Docker engine to be used. `linux` specifies the Linux engine. `windows` specifies the Windows engine.               |
-| `analyticsEnabled`                | If `value` is true, allow Docker Desktop Enterprise to sends diagnostics, crash reports, and usage data. This information helps Docker improve and troubleshoot the application.                |
-| `exposeDockerAPIOnTCP2375`        | Exposes Docker API on a specified port. In this example, setting 'locked' to `true` exposes the Docker API on port 2375. **Warning:** This is unauthenticated and should only be enabled if protected by suitable firewall rules.|
-| `dockerCliOptions`                | Specifies key-value pairs in the user's `%HOME%\.docker\config.json` file. In the sample code provided, the orchestration for docker stack commands is set to `swarm` rather than `kubernetes`. |
-| `proxy`                           | The `http` setting specifies the HTTP proxy setting. The `https` setting specifies the HTTPS proxy setting. The `exclude` setting specifies a comma-separated list of hosts and domains to bypass the proxy. **Warning:** This parameter should be locked after being set: `locked: "true"`.                 |
-| `linuxVM`                         | Parameters and settings related to the Linux VM - grouped together in this example for convenience.          |
-| `cpus`                            | Specifies the default number of virtual CPUs for the VM. If the physical machine has only 1 core, the default value is set to 1.    |
-| `memoryMiB`                       | Specifies the amount of memory in MiB (1 MiB = 1048576 bytes) allocated for the VM.
-| `swapMiB`                         | Specifies the amount of memory in MiB (1 MiB = 1048576 bytes) allocated for the swap file.                |
-| `dataFolder`                      | Specifies the root folder where Docker Desktop should put VM disk files.    |
-| `diskSizeMiB`                     | Specifies the amount of disk storage in MiB (1 MiB = 1048576 bytes) allocated for images and containers.                       |
-| `hypervCIDR`                      | Specifies the subnet used for Hyper-V networking. The chosen subnet must not conflict with other resources on your network.                          |
-| `vpnkitCIDR`                      | Specifies the subnet used for VPNKit networking and drive sharing. The chosen subnet must not conflict with other resources on your network.                          |
-| `useDnsForwarder`                 | If `value` is set to `true`, this automatically determines the upstream DNS servers based on the host's network adapters.      |
-| `dns`                             | If `value` for `useDnsForwarder` is set to `false`, the Linux VM uses the server information in this `value` setting for DNS resolution.                       |
-| `dockerDaemonOptions`             | Overrides the options in the Linux daemon config file. For more information, see [Docker engine reference](/engine/reference/commandline/dockerd/#daemon-configuration-file).      |
-| (End of `linuxVM` section.)       |                                   |
-| `windows`                         | Parameters and settings related to the Windows daemon-related options - grouped together in this example for convenience.          |
-| `dockerDaemonOptions`             | Overrides the options in the Windows daemon config file. For more information, see [Docker engine reference](/engine/reference/commandline/dockerd/#daemon-configuration-file).     |
-| (End of `windows` section.)       |                                   |
-| `kubernetes`                      | Parameters and settings related to kubernetes options - grouped together here for convenience.                  |
-| `enabled`                         | If `locked` is set to `true`, the Kubernetes cluster starts when Docker Desktop Enterprise is started.                          |
-| `showSystemContainers`            | If true, displays Kubernetes internal containers when running docker commands such as `docker ps`.     |
-| `podNetworkCIDR`                  | This is currently unimplemented. `locked` must be set to true.     |
-| `serviceCIDR`                     | This is currently unimplemented. `locked` must be set to true.     |
-| (End of `kubernetes` section.)    |                                   |
-|`template`|Parameters and settings related to Docker Template and Application Designer - grouped together in this example for convenience. |
-|`defaultOrg`| Specifies the default organization to be used in Docker Template and Docker Application Designer. If `locked` is set to `true`, the Kubernetes cluster starts when Docker Desktop Enterprise is started. |
-|`defaultRegistry`|Specifies the default registry to be used in Docker Template and Application Designer.|
-|`repositories`|Lists the repositories that are allowed.|
-| `filesharingDirectories`          | The host folders that users can bind-mount in containers.         |
-
-### File format update
-
-#### From version 1 to 2
-
-Docker Desktop Enterprise 2.3.0.0-ent contains a change in the configuration file format.
-
-If you haven’t made any changes to the `admin-settings.json` file in the previous installation, you can simply delete it and Docker Desktop will re-create it automatically.
-Otherwise manual steps are required to update the `admin-settings.json` file.
-
-1. Increase the value of the `configurationFileVersion` field from 1 to 2, i.e. before:
-    ```json
-   {
-      "configurationFileVersion": 1,
-      ...
-   }
-    ```
-    after:
-    ```json
-   {
-      "configurationFileVersion": 2,
-      ...
-   }
-    ```
-
-2. Replace the `sharedDrives` and `sharedFolders` fields with a single `filesharingDirectories` field, e.g. before:
-    ```json
-   {
-      ...
-      "sharedDrives": {
-        "locked": true,
-        "value": ["C"]
-      },
-      "sharedFolders": ["%USERPROFILE%"]
-   }
-    ```
-    after:
-    ```json
-   {
-      ...
-      "filesharingDirectories": {
-        "locked": true,
-        "value": ["C:", "%USERPROFILE%"]
-      }
-   }
-    ```
-

desktop/enterprise/admin/install/mac.md

@@ -1,111 +0,0 @@
----
-title: Install Docker Desktop Enterprise on Mac
-description: Learn about Docker Desktop Enterprise
-keywords: Docker EE, Mac, Docker Desktop, Enterprise
-redirect_from:
-- /ee/desktop/admin/install/mac/
----
-
-This page contains information about the system requirements and specific instructions that help you install Docker Desktop Enterprise (DDE) on Mac. If you are using the Community version of Docker Desktop, you must uninstall Docker Desktop Community in order to install DDE.
-
-[Download Docker Desktop Enterprise for Mac](https://download.docker.com/mac/enterprise/Docker.pkg){: .button .outline-btn}
-
-> **Note:** By downloading DDE, you agree to the terms of the [Docker Software End User License Agreement](https://www.docker.com/legal/docker-software-end-user-license-agreement){: target="_blank" rel="noopener" class="_"} and the [Docker Data Processing Agreement (DPA)](https://www.docker.com/legal/data-processing-agreement){: target="_blank" rel="noopener" class="_"}.
-
-## System requirements
-
-- Mac hardware must be a 2010 or newer model, with Intel’s hardware support for memory management unit (MMU) virtualization, including Extended Page Tables (EPT) and Unrestricted Mode. You can check to see if your machine has this support by running the following command in a terminal: `sysctl kern.hv_support`
-
-- macOS must be version 10.13 or newer. We recommend upgrading to the latest version of macOS.
-
-    If you experience any issues after upgrading your macOS to version 10.15, you must install the latest version of Docker Desktop to be compatible with this version of macOS.
-
-- At least 4GB of RAM
-
-- VirtualBox prior to version 4.3.30 must NOT be installed (it is incompatible with Docker for Mac). If you have a newer version of VirtualBox installed, it’s fine.
-
-> **Note:** Docker supports Docker Desktop Enterprise on the most recent versions of macOS. That is, the current release of macOS and the previous two releases. As new major versions of macOS are made generally available, Docker will stop supporting the oldest version and support the newest version of macOS (in addition to the previous two releases).
-
-## Installation
-
-The DDE installer includes Docker Engine, Docker CLI client, and Docker Compose.
-
-Double-click the `.pkg` file to begin the installation and follow the on-screen instructions. When the installation is complete, click the Launchpad icon in the Dock and then **Docker** to start Docker Desktop.
-
-Mac administrators can use the command line option `\$ sudo installer -pkg Docker.pkg -target /` for fine tuning and mass installation. After running this command, you can start Docker Desktop from the Applications folder on each machine.
-
-Administrators can configure additional settings by modifying the administrator configuration file. For more information, see [Configure Desktop Enterprise for Mac](../configure/mac-admin.md).
-
-## License file
-
-Install the Docker Desktop Enterprise license file at the following location:
-
-`/Library/Group Containers/group.com.docker/docker_subscription.lic`
-
-You must create the path if it doesn't already exist. If the license file is missing, you will be asked to provide it when you try to run Docker Desktop Enterprise. Contact your system administrator to obtain the license file.
-
-## Firewall exceptions
-
-Docker Desktop Enterprise requires the following firewall exceptions. If you do not have firewall access, or are unsure about how to set firewall exceptions, contact your system administrator.
-
-- The process `com.docker.vpnkit` proxies all outgoing container TCP and
-    UDP traffic. This includes Docker image downloading but not DNS
-    resolution, which is performed over a Unix domain socket connected
-    to the `mDNSResponder` system service.
-
-- The process `com.docker.vpnkit` binds external ports on behalf of
-    containers. For example, `docker run -p 80:80 nginx` binds port 80 on all
-    interfaces.
-
-- If using Kubernetes, the API server is exposed with TLS on
-    `127.0.0.1:6443` by `com.docker.vpnkit`.
-
-## Version packs
-
-Docker Desktop Enterprise is bundled with default version pack [Enterprise 3.0 (Docker Engine 19.03 / Kubernetes 1.14)](https://download.docker.com/mac/enterprise/enterprise-3.0.ddvp). System administrators can install version packs using a command line tool to use a different version of the Docker Engine and Kubernetes for development work:
-
-- [Docker Enterprise 2.0 (17.06/Kubernetes 1.8.11)](https://download.docker.com/mac/enterprise/enterprise-2.0.ddvp)
-
-- [Docker Enterprise 2.1 (18.09/Kubernetes 1.11.5)](https://download.docker.com/mac/enterprise/enterprise-2.1.ddvp)
-
-For information on using the CLI tool for version pack installation, see [Command line installation](#command-line-installation).
-
-> **Note:** It is not possible to install the version packs using the Docker Desktop user interface or by double-clicking the `.ddvp` file.
-
-Available version packs are listed within the **Version Selection** option in the Docker Desktop menu. If more than one version pack is installed, you can select the corresponding entry to work with a different version pack. After you select a different version pack, Docker Desktop restarts and the selected Docker Engine and Kubernetes versions are used.
-
-If more than one version pack is installed, you can select the corresponding entry to work with a different version pack. After you select a different version pack, Docker Desktop restarts and the selected Docker Engine and Kubernetes versions are used.
-
-## Command line installation
-
-System administrators can use a command line executable to install and uninstall Docker Desktop Enterprise and version packs.
-
-When you install Docker Desktop Enterprise, the command line tool is installed at the following location:
-
-[ApplicationPath]/Contents/Resources/bin/dockerdesktop-admin
-
->**Note:** Command line installation is supported for administrators only. You must have `sudo` access privilege to run the CLI commands.
-
-### Version-pack install
-
-Run the following command to install or upgrade a version pack to the version contained in the specified `.ddvp` archive:
-
-    sudo /Applications/Docker.app/Contents/Resources/bin/dockerdesktop-admin version-pack install [path-to-archive]
-
- >**Note:** You must stop Docker Desktop before installing a version pack.
-
-### Version-pack uninstall
-
- Run the following command to uninstall the specified version pack:
-
-    sudo /Applications/Docker.app/Contents/Resources/bin/dockerdesktop-admin version-pack uninstall [version-pack-name]
-
->**Note:** You must stop Docker Desktop before uninstalling a version pack.
-
-### Application uninstall
-
-Run the following command to uninstall the application:
-
-    sudo /Applications/Docker.app/Contents/Resources/bin/dockerdesktop-admin app uninstall
-
-The `sudo` command uninstalls files such as version packs that are installed by an administrator, but are not accessible by users.

desktop/enterprise/admin/install/windows.md

@@ -1,132 +0,0 @@
----
-title: Install Docker Desktop Enterprise on Windows
-description: Learn about Docker Desktop Enterprise
-keywords: Docker EE, Windows, Docker Desktop, Enterprise
-redirect_from:
-- /ee/desktop/admin/install/windows/
----
-
-This page contains information about the system requirements and specific instructions that help you install Docker Desktop Enterprise (DDE) on Windows. If you are using the Community version of Docker Desktop, you must uninstall Docker Desktop Community in order to install DDE.
-
-[Download Docker Desktop Enterprise for Windows](https://download.docker.com/win/enterprise/DockerDesktop.msi){: .button .outline-btn}
-
->**Note:** By downloading DDE, you agree to the terms of the [Docker Software End User License Agreement](https://www.docker.com/legal/docker-software-end-user-license-agreement){: target="_blank" rel="noopener" class="_"} and the [Docker Data Processing Agreement (DPA)](https://www.docker.com/legal/data-processing-agreement){: target="_blank" rel="noopener" class="_"}.
-
-## System requirements
-
-- Windows 10 Pro or Enterprise version 15063 or later.
-
-- Hyper-V and Containers Windows features must be enabled **before** installing DDE.
-
-    To enable Hyper-V and Containers features using PowerShell, run the following commands as Administrator:
-
-    `Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All`
-
-    `Enable-WindowsOptionalFeature -Online -FeatureName Containers -All`
-
-    After running the commands, reboot your system.
-
-- The following hardware prerequisites are required to successfully run Client
-Hyper-V on Windows 10:
-
-  - 64 bit processor with [Second Level Address Translation (SLAT)](https://en.wikipedia.org/wiki/Second_Level_Address_Translation)
-
-  - 4GB system RAM
-
-  - BIOS-level hardware virtualization support must be enabled in the
-    BIOS settings:
-
-![Virtualization Technology (VTx) must be enabled in BIOS settings](../../images/windows-prereq.png "BIOS setting information for hardware virtualization support")
-
-> **Note:** Docker supports Docker Desktop Enterprise on Windows based on Microsoft’s support lifecycle for Windows 10 operating system. For more information, see the [Windows lifecycle fact sheet](https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet).
-
-## Installation
-
-The Docker Desktop Enterprise installer includes Docker Engine, Docker CLI client, and Docker Compose.
-
-Double-click the `.msi` file to begin the installation and follow the on-screen instructions. When the installation is complete, select **Docker Desktop** from the Start menu to start Docker Desktop.
-
-For information about installing DDE using the command line, see [Command line installation](#command-line-installation).
-
-## License file
-
-Install the Docker Desktop Enterprise license file at the following location:
-
-    %ProgramData%\DockerDesktop\docker_subscription.lic
-
-You must create the path if it doesn't already exist. If the license file is missing, you will be asked to provide it when you try to run Docker Desktop Enterprise. Contact your system administrator to obtain the license file.
-
-## Firewall exceptions
-
-Docker Desktop Enterprise requires the following firewall exceptions. If you do not have firewall access, or are unsure about how to set firewall exceptions, contact your system administrator.
-
-- The process `com.docker.vpnkit` proxies all outgoing container TCP and
-    UDP traffic. This includes Docker image downloading but not DNS
-    resolution, which is performed over a loopback TCP and UDP connection
-    to the main application.
-
-- The process `com.docker.vpnkit` binds external ports on behalf of
-    containers. For example, `docker run -p 80:80 nginx` binds port 80 on all
-    interfaces.
-
-- If using Kubernetes, the API server is exposed with TLS on `127.0.0.1:6445` by `com.docker.vpnkit`.
-
-## Version packs
-
-Docker Desktop Enterprise is bundled with default version pack [Enterprise 3.0 (Docker Engine 19.03 / Kubernetes 1.14)](https://download.docker.com/win/enterprise/enterprise-3.0.ddvp). System administrators can install version packs using a command line tool to use a different version of the Docker Engine and Kubernetes for development work:
-
-- [Docker Enterprise 2.0 (17.06/Kubernetes 1.8.11)](https://download.docker.com/win/enterprise/enterprise-2.0.ddvp)
-
-- [Docker Enterprise 2.1 (18.09/Kubernetes 1.11.5)](https://download.docker.com/win/enterprise/enterprise-2.1.ddvp)
-
-For information on using the CLI tool for version pack installation, see [Command line installation](#command-line-installation).
-
-Available version packs are listed within the **Version Selection** option in the Docker Desktop menu. If more than one version pack is installed, you can select the corresponding entry to work with a different version pack. After you select a different version pack, Docker Desktop restarts and the selected Docker Engine and Kubernetes versions are used.
-
-## Command line installation
-
->**Note:** Command line installation is supported for administrators only. You must have `administrator` access to run the CLI commands.
-
-System administrators can use the command line for mass installation and fine tuning the Docker Desktop Enterprise deployment. Run the following command as an administrator to perform a silent installation:
-
-    msiexec /i DockerDesktop.msi /quiet
-
-You can also set the following properties:
-
-- `INSTALLDIR [string]:` configures the folder to install Docker Desktop to (default is C:\Program Files\Docker\Docker)
-- `STARTMENUSHORTCUT [yes|no]:` specifies whether to create an entry in the Start menu for Docker Desktop (default is yes)
-- `DESKTOPSHORTCUT [yes|no]:` specifies whether to create a shortcut on the desktop for Docker Desktop (default is yes)
-
-For example:
-
-    msiexec /i DockerDesktop.msi /quiet STARTMENUSHORTCUT=no INSTALLDIR=”D:\Docker Desktop”
-
-Docker Desktop Enterprise includes a command line executable to install and uninstall version packs. When you install DDE, the command line tool is installed at the following location:
-
-    [ApplicationPath]\dockerdesktop-admin.exe
-
-### Version-pack install
-
-Run the following command to install or upgrade a version pack to the version contained in the specified `.ddvp` archive:
-
-    dockerdesktop-admin.exe -InstallVersionPack=['path-to-archive']
-
->**Note:** You must stop Docker Desktop before installing a version pack.
-
-### Version-pack uninstall
-
-Run the following command to uninstall the specified version pack:
-
-    dockerdesktop-admin.exe -UninstallVersionPack=[version-pack-name|'path-to-archive']
-
->**Note:** You must stop Docker Desktop before uninstalling a version pack.
-
-### Application uninstall
-
-To uninstall the application:
-
-1. Open the **Add or remove programs** dialog
-
-1. Select **Docker Desktop** from the **Apps & features** list.
-
-1. Click **Uninstall**.

desktop/enterprise/app-designer.md

@@ -1,44 +0,0 @@
----
-title: Application Designer
-description: Docker Desktop Enterprise Application Designer
-keywords: Docker EE, Windows, Mac, Docker Desktop, Enterprise, templates, designer
-redirect_from:
-- /ee/desktop/app-designer/
----
-
-## Overview
-
-The Application Designer helps Docker developers quickly create new
-Docker apps using a library of templates. To start the Application
-Designer, select the **Design new application** menu entry.
-
-![The Application Designer lets you choose an existing template or create a custom application.](/desktop/enterprise/images/app-design-start.png "Application Designer")
-
-The list of available templates is provided:
-
-![You can tab through the available application templates. A description of each template is provided.](/desktop/enterprise/images/app-design-choose.png "Available templates for application creation")
-
-After selecting a template, you can then customize your application, For
-example, if you select **Flask / NGINX / MySQL**, you can then
-
-- select a different version of python or mysql; and
-
-- choose different external ports:
-
-![You can customize your application, which includes specifying database, proxy, and other details.](/desktop/enterprise/images/app-design-custom.png "Customizing your application")
-
-You can then name your application and customize the disk location:
-
-![You can also customize the name and location of your application.](/desktop/enterprise/images/app-design-custom2.png "Naming and specifying a location for your application")
-
-When you select **Assemble**, your application is created.
-
-![When you assemble your application, a status screen is displayed.](/desktop/enterprise/images/app-design-test.png "Assembling your application")
-
-Once assembled, the following screen allows you to run the application. Select **Run application** to pull the images and start the containers:
-
-![When you run your application, the terminal displays output from the application.](/desktop/enterprise/images/app-design-run.png "Running your application")
-
-Use the corresponding buttons to start and stop your application. Select **Open in Finder** on Mac or **Open in Explorer** on Windows to
-view application files on disk. Select **Open in Visual Studio Code** to open files with an editor. Note that debug logs from the application are displayed in the lower part of the Application Designer
-window.

desktop/enterprise/index.md

@@ -1,63 +1,23 @@
 ---
-title: Docker Desktop Enterprise overview
-description: Learn about Docker Desktop Enterprise
-keywords: Docker EE, Windows, Mac, Docker Desktop, Enterprise
+title: Docker Desktop Enterprise
+description: Docker Desktop Enterprise
+keywords: Docker Desktop Enterprise
+sitemap: false
 redirect_from:
 - /ee/desktop/
+- /desktop/enterprise/release-notes/
+- /desktop/enterprise/admin/install/mac/
+- /desktop/enterprise/admin/configure/mac-admin/
+- /desktop/enterprise/admin/configure/windows-admin/
+- /desktop/enterprise/user/mac-user/
+- /desktop/enterprise/user/windows-user/
+- /desktop/enterprise/app-designer/
+- /desktop/enterprise/troubleshoot/mac-issues/
+- /desktop/enterprise/troubleshoot/windows-issues/
 ---
 
-Welcome to Docker Desktop Enterprise. This page contains information about the Docker Desktop Enterprise (DDE) release. For information about Docker Desktop Community, see:
+Docker Desktop Enterprise (DDE) has been deprecated and is no longer in active development. Please use [Docker Desktop](../index.md) Community instead.
 
-- [Docker Desktop for Mac (Community)](../../docker-for-mac/index.md)
+If you are an existing DDE customer, use our [Support form](https://hub.docker.com/support/desktop/){: target="_blank" rel="noopener" class="_"} to request a transition to one of our new [subscription plans](https://www.docker.com/pricing){: target="_blank" rel="noopener" class="_"}.
 
-- [Docker Desktop for Windows (Community)](../../docker-for-windows/index.md)
-
-Docker Desktop Enterprise provides local development, testing, and building of Docker applications on Mac and Windows. With work performed locally, developers can leverage a rapid feedback loop before pushing code or Docker images to shared servers / continuous integration infrastructure.
-
-Docker Desktop Enterprise takes Docker Desktop Community, formerly known as Docker for Windows and Docker for Mac, a step further with simplified enterprise application development and maintenance. With DDE, IT organizations can ensure developers are working with the same version of Docker Desktop and can easily distribute Docker Desktop to large teams using third-party endpoint management applications. With the Docker Desktop graphical user interface (GUI), developers do not have to work with lower-level Docker commands and can auto-generate Docker artifacts.
-
-Installed with a single click or command line command, Docker Desktop Enterprise is integrated with the host OS framework, networking, and filesystem. DDE is also designed to integrate with existing development environments (IDEs) such as Visual Studio and IntelliJ. With support for defined application templates, Docker Desktop Enterprise allows organizations to specify the look and feel of their applications.
-
-Feature comparison of Docker Desktop Community versus Docker Desktop Enterprise:
-
-  | Feature                     | Docker Desktop (Community) | Docker Desktop Enterprise |
-  | :-------------------------  |:--------------------------:|:-------------------------:|
-  | Docker Engine               | X                          |  X                        |
-  | Certified Kubernetes        | X                          |  X                        |
-  | Docker Compose              | X                          |  X                        |
-  | CLI                         | X                          |  X                        |
-  | Windows and Mac support     | X                          |  X                        |
-  | Version Selection           |                            |  X                        |
-  | Application Designer        |                            |  X                        |
-  | Custom application templates|                            |  X                        |
-  | Docker Assemble             |                            |  X                        |
-  | Device management           |                            |  X                        |
-  | Administrative control      |                            |  X                        |
-
-## Docker Desktop Enterprise features
-
-The following section lists features that are exclusive to Docker Desktop Enterprise:
-
-### Version Selection
-
-Configurable version packs ensure the local instance of Docker Desktop Enterprise is a precise copy of the production environment where applications are deployed.
-
-System administrators can install version packs using a built-in command line tool. Once installed, developers can switch between versions of Docker and Kubernetes with a single click and ensure Docker and Kubernetes versions match UCP cluster versions.
-
-### Application Designer
-
- Application Designer provides a library of application and service templates to help developers quickly create new Docker applications.
-
-### Application templates
-
-Application templates allow you to choose a technology stack and focus on business logic and code, and require only minimal Docker syntax knowledge. Template support includes .NET, Spring, and more.
-
-### Device management
-
-The Docker Desktop Enterprise installer is available as standard MSI (Windows) and PKG (Mac) downloads, which allows administrators to script an installation across many developer workstations.
-
-### Administrative control
-
-IT organizations can specify and lock configuration parameters for the creation of  standardized development environments, including disabling drive sharing.
-
-Developers can then run commands using the command line without worrying about configuration settings.
+If you are looking to deploy Docker Desktop at scale, contact us on [pricingquestions@docker.com](mailto:pricingquestions@docker.com){: target="_blank" rel="noopener" class="_"}.

desktop/enterprise/release-notes.md

@@ -1,286 +0,0 @@
----
-title: Docker Desktop Enterprise release notes
-description: Release notes for Docker Desktop Enterprise
-keywords: Docker Desktop Enterprise, Windows, Mac, Docker Desktop, Enterprise,
-toc_min: 1
-toc_max: 2
-redirect_from:
-- /ee/desktop/release-notes/
----
-
-This page contains information about the new features, improvements, known issues, and bug fixes in the Docker Desktop Enterprise release. Documentation is updated for each release. We suggest that you regularly visit this page to learn about updates.
-
-For information on system requirements, installation, and download, see:
-
-- [Install Docker Desktop Enterprise on Mac](admin/install/mac.md)
-- [Install Docker Desktop Enterprise on Windows](admin/install/windows.md)
-
-For Docker Engine release notes, see [Docker Engine release notes](../../engine/release-notes/index.md).
-
-## Version 2.3.0.0
-2020-04-22
-
-Docker Desktop Enterprise 2.3.0.0 contains a Kubernetes upgrade. Note that your local Kubernetes cluster in Version Pack 3.0 will be reset after installing this version.
-
-This version includes all the bug fixes and minor changes between Docker Desktop Community versions 2.1.0.1 and 2.3.0.0. For details see:
-- [Docker Desktop Community release notes on Mac](../../docker-for-mac/release-notes.md) 
-- [Docker Desktop Community release notes on Windows](../../docker-for-windows/release-notes.md) 
-
-### Bug fixes and minor changes
-
-- Windows: in the `admin-settings.json` configuration file, the `sharedDrives` and `sharedFolders` fields have been replaced by a unique `filesharingDirectories` field.
-- Mac: in the `admin-settings.json` configuration file, the `filesharingDirectories` has been moved out of the `linuxVM` section.
-- The `admin-settings.json` configuration file `configurationFileVersion` field value has been increased from 1 to 2.
-
-### Known issue
-
-Docker Desktop Enterprise 2.3.0.0 contains a change in the configuration file format.
-
-For more information, see:
-- [Update Docker Desktop Enterprise configuration file from version 1 to 2 on Mac](admin/configure/mac-admin.md#from-version-1-to-2)
-- [Update Docker Desktop Enterprise configuration file from version 1 to 2 on Windows](admin/configure/windows-admin.md#from-version-1-to-2)
-
-## Version 2.1.0.9
-2020-03-13
-
-### Bug fixes and minor changes
-
-- Windows: Security fix - Diagnostics were collected with Administrator privileges, which led to a possible privilege escalation on systems where the Docker Desktop user was not an administrator.
-
-## Version 2.1.0.8
-2019-11-14
-
-Docker Desktop Enterprise 2.1.0.8 contains a Kubernetes upgrade. Note that your local Kubernetes cluster in Version Pack 3.0 will be reset after installing this version.
-
-### Upgrades
-
-- [Docker 19.03.5](/engine/release-notes/#19035) in Version Pack Enterprise 3.0
-- [Kubernetes 1.14.8](https://github.com/kubernetes/kubernetes/releases/tag/v1.14.8) in Version Pack Enterprise 3.0
-- [Docker 18.09.11](/engine/release-notes/#180911) in Version Pack Enterprise 2.1
-- [Docker 17.06.2-ee-25](/engine/release-notes/#17062-ee-25) in Version Pack Enterprise 2.0
-- [Go 1.12.13](https://golang.org/doc/devel/release.html#go1.12)
-
-## Version 2.1.0.7
-2019-10-18
-
-### Upgrades
-
-[Docker 19.03.4](/engine/release-notes/) in Version Pack Enterprise 3.0
-
-## Version 2.1.0.6
-2019-10-08
-
-Docker Desktop Enterprise 2.1.0.6 contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing this version.
-
-### Upgrades
-
-- [Docker 19.03.3](/engine/release-notes/) in Version Pack Enterprise 3.0
-- [Kubernetes 1.14.7](https://github.com/kubernetes/kubernetes/releases/tag/v1.14.7) in Version Pack Enterprise 3.0
-- [Go 1.12.10](https://github.com/golang/go/issues?q=milestone%3AGo1.12.10+label%3ACherryPickApproved)
-- Application Designer 0.1.8
-
-### Bug fixes and minor changes
-
-- Windows: Docker Desktop no longer tries to modify the `/etc/hosts` file inside Windows containers to add `*.docker.internal` DNS entries.
-
-## Version 2.1.0.5
-2019-09-16
-
-### Bug fixes and minor changes
-
- - Mac: All binaries included in Docker Desktop are now notarized so that they can run on macOS Catalina. For more information, see [Notarization Requirement for Mac Software](https://developer.apple.com/news/?id=06032019i).
-
-## Version 2.1.0.4
-2019-09-03
-
-Docker Desktop Enterprise 2.1.0.3 contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing this version.
-
-### Upgrades
-
-- [Docker 19.03.2](/engine/release-notes/) in Version Pack Enterprise 3.0
-- [Kubernetes 1.14.6](https://github.com/kubernetes/kubernetes/releases/tag/v1.14.6) in Version Pack Enterprise 3.0
-- [Go 1.12.9](https://github.com/golang/go/issues?q=milestone%3AGo1.12.9+label%3ACherryPickApproved) in Version Pack Enterprise 3.0
-- [Qemu 4.1.0](https://github.com/docker/binfmt) to cross-compile ARM devices
-- Application Designer 0.1.6
-- Mac: [Hyperkit 0.20190802](https://github.com/moby/hyperkit/releases/tag/v0.20190802)
-
-### Bug fixes and minor changes
-
-- Restricted the `cluster-admin` role on local Kubernetes cluster to `kube-system` namespace.
-- Mac: Docker Desktop checks the `admin-settings.json` file and enforces the CLI config whenever Docker Engine is restarted.
-- Windows: Updated the Access Control List (ACL) on `cli-plugins` and `version-bin` folders to ensure only administrators have read/write access to these folders.
-
-## Version 2.1.0.2
-2019-07-26
-
-### Upgrades
-
-- [Docker 19.03.1](/engine/release-notes/) in Version Pack Enterprise 3.0.
-
-## Version 2.1.0.1
-2019-07-22
-
-Docker Desktop Enterprise 2.1.0.1 contains a Kubernetes upgrade. Note that your local Kubernetes cluster will be reset after installing this release.
-
-### Upgrades
-
-- [Docker 19.03.0](/engine/release-notes/) in Version Pack Enterprise 3.0
-- [Kubernetes 1.14.3](https://github.com/kubernetes/kubernetes/releases/tag/v1.14.3) in Version Pack Enterprise 3.0
-- [Compose on Kubernetes 0.4.23](https://github.com/docker/compose-on-kubernetes/releases/tag/v0.4.23) in Version Pack Enterprise 3.0
-- [Docker Compose 1.24.1](https://github.com/docker/compose/releases/tag/1.24.1)
-- [Docker 18.09.8](/engine/release-notes/) in Version Pack Enterprise 2.1
-- [Docker 17.06.2-ee-23](/engine/release-notes/) in Version Pack Enterprise 2.0
-- [Docker Credential Helpers 0.6.3](https://github.com/docker/docker-credential-helpers/releases/tag/v0.6.3)
-- [Application Designer 0.1.4](app-designer.md)
-
-### Known issue
-
-When you sign out of Windows while Docker Desktop is still running, and then sign in and start Docker Desktop, attempts to run Docker commands that rely on network connections can fail. For example, the command `docker pull alpine` returns `Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)`.
-
-Note that this issue occurs only when you sign out of Windows and not when you shut down or restart Windows.
-
-Workaround: After signing back into Windows, when Docker Desktop has started, right-click the Docker menu from the systray and then select Quit Docker Desktop. When this is complete, start Docker Desktop normally.
-
-## Version 2.0.0.6
-2019-06-06
-
-### Upgrades
-
-- [Docker 19.03.0-rc2](/engine/release-notes/) in Version Pack Enterprise 3.0
-- Application Designer 0.1.3
-
-### Bug fixes and minor changes
-
-- Application Designer/ Docker Template CLI: The `DefaultServer` preference has been renamed to `DefaultRegistry`.
-- Windows: Docker Desktop now allows administrators to specify authorized named pipes that can be mounted on Windows containers.
-- Windows: Docker Desktop checks for stored credentials at startup before attempting to mount any shared drives. This prompts users to reenter the credentials if they are invalid.
-- Mac: Docker Deskop does not send DNS queries for `docker-desktop.<domain>` every 10s. It relies on the host's DNS domain search order rather than trying to replicate it inside the VM.
-- Mac: Docker Desktop now uses a separate thread to move its storage to a different disk. This allows the UI to remain responsive during the disk move. Fixes [docker/for-mac#3592](https://github.com/docker/for-mac/issues/3592)
-
-## Version 2.0.0.5
-2019-05-30
-
-### Upgrades
-
-- [Docker 19.03.0-rc1](/engine/release-notes/) in Enterprise 3.0 version pack
-- Application Designer 0.1.2
-- [Qemu 4.0.0](https://github.com/docker/binfmt) to cross-compile ARM devices
-
-### Bug fixes and minor changes
-
-- Application Designer now allows users to copy and paste application logs.
-- Users can browse the scaffold logs when scaffolding a new application using the Application Designer.
-- Application Designer allows users to set preferences, including the default organization and registry.
-- Docker Desktop admins can enforce Application Designer preferences using the `admin-settings.json` file.
-- Security improvements: Docker Desktop now checks TLS certificates for the target endpoints when using `kubectl`.
-- Fixed an issue where Visual Studio Code IDE path was not detected properly.
-
-## Version 2.0.0.4
-2019-05-16
-
-### Upgrades
-
-- [Docker 19.03.0-beta4](/engine/release-notes/) in Enterprise 3.0 version pack
-- [Docker 18.09.6](/engine/release-notes/), [Kubernetes 1.11.10](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#v11110) in Enterprise 2.1 version pack
-- [LinuxKit v0.7](https://github.com/linuxkit/linuxkit/releases/tag/v0.7)
-
-### Bug fixes and minor changes
-
-- Fixed a stability issue with the DNS resolver.
-- Fixed a race condition where Kubernetes sometimes failed to start after restarting the application.
-- Fixed a bug that causes Docker Compose to fail when a user logs out after logging in. See [docker/compose#6517](https://github.com/docker/compose/issues/6517)
-- Improved the reliability of `com.docker.osxfs trace` performance profiling command.
-- Docker Desktop now supports large lists of resource DNS records on Mac. See [docker/for-mac#2160](https://github.com/docker/for-mac/issues/2160#issuecomment-431571031).
-- Users can now run a Docker registry in a container. See [docker/for-mac#3611](https://github.com/docker/for-mac/issues/3611).
-- For Linux containers on Windows (LCOW), one physical computer system running Windows 10 Professional or Windows 10 Enterprise version 1809 or later is required.
-- Added a dialog box during startup when a shared drive fails to mount. This allows users to retry mounting the drive or remove it from the shared drive list.
-- Removed the ability to log in using an email address as a username as this is not supported by the Docker command line.
-
-## Version 2.0.0.3
-2019-04-26
-
-### Upgrades
-
-- [Docker Engine 19.03.0-beta2](/engine/release-notes/) for Version Pack Enterprise 3.0.
-
-## Version 2.0.0.2
-2019-04-19
-
-**WARNING:** You must upgrade the previously installed Version Packs to the latest revision.
-
-### New
-
-- Version Pack Enterprise 3.0 with [Docker Engine 19.03.0-beta1](/engine/release-notes/) and [Kubernetes 1.14.1](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.14.md#changelog-since-v1141)
-
-- Application Designer now includes new templates for AngularJS and VueJS.
-
-### Upgrades
-
-- [Docker Compose 1.24.0](https://github.com/docker/compose/releases/tag/1.24.0)
-- [Docker Engine 18.09.5](/engine/release-notes/), [Kubernetes 1.11.7](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.11.md#v1117) and [Compose on Kubernetes 0.4.22](https://github.com/docker/compose-on-kubernetes/releases/tag/v0.4.22) for Version Pack Enterprise 2.1
-- [Docker Engine 17.06.2-ee-21](/engine/release-notes/) for Version Pack Enterprise 2.0
-
-### Bug fixes and minor changes
-
-- For security, only administrators can install or upgrade Version Packs using the `dockerdesktop-admin` tool.
-- Truncate UDP DNS responses which are over 512 bytes in size
-- Fixed airgap install of kubernetes in version pack enterprise-2.0
-- Reset to factory default now resets to admin defaults
-
-### Known issues
-
-- The Docker Template CLI plugin included in this version is an outdated version of the plugin and will fail when scaffolding templates. Note that the Application Designer is not affected by this outdated version of the CLI plugin.
-
-## Version 2.0.0.1
-2019-03-01
-
-**WARNING:** You must upgrade the previously installed Version Packs to the latest revision.
-
-### Windows
-
-#### Upgrades
-
-- Docker 18.09.3 for Version Pack Enterprise 2.1, fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736)
-- Docker 17.06.2-ee-20 for Version Pack Enterprise 2.0, fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736)
-
-#### Bug fixes and minor changes
-
-- Fixed port 8080 that was used on localhost when starting Kubernetes.
-- Fixed Hub login through the desktop UI not sync with login through `docker login` command line.
-- Fixed crash in system tray menu when the Hub login fails or Air gap mode.
-
-### Mac
-
-#### New features
-
-- Added ability to list all installed version packs with the admin CLI command `dockerdesktop-admin version-pack list`.
-- `dockerdesktop-admin app uninstall` will also remove Docker Desktop user files.
-
-#### Upgrades
-
-- Docker 18.09.3 for Version Pack Enterprise 2.1, fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736)
-- Docker 17.06.2-ee-20 for Version Pack Enterprise 2.0, fixes [CVE-2019-5736](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5736)
-
-#### Bug fixes and minor changes
-
-- Fixed port 8080 that was used on localhost when starting Kubernetes.
-- Improved error messaging to suggest running diagnostics / resetting to factory default only when it is appropriate.
-
-## Version 2.0.0.0
-2019-01-31
-
-### New features
-
-- **Version selection**: Configurable version packs ensure the local
-    instance of Docker Desktop Enterprise is a precise copy of the
-    production environment where applications are deployed, and
-    developers can switch between versions of Docker and
-    Kubernetes with a single click.
-
-- **Application Designer**: Application templates allow you to choose a
-    technology and focus on business logic. Updates can be made with
-    minimal syntax knowledge.
-
-- **Device management**: The Docker Desktop Enterprise installer is available as standard MSI (Win) and PKG (Mac) downloads, which allows administrators to script an installation across many developer machines.
-
-- **Administrative control**: IT organizations can specify and lock configuration parameters for creation of a standardized development environment, including disabling drive sharing and limiting version pack installations. Developers run commands in the command line without worrying about configuration settings.

desktop/enterprise/troubleshoot/mac-issues.md

@@ -1,80 +0,0 @@
----
-title: Troubleshoot Docker Desktop Enterprise issues on Mac
-description: Troubleshoot Mac issues
-keywords: Troubleshoot, diagnose, Mac, issues, Docker Enterprise, Docker Desktop, Enterprise
-redirect_from:
-- /ee/desktop/troubleshoot/mac-issues/
----
-
-This page contains information on how to diagnose Docker Desktop Enterprise (DDE) issues on Mac.
-
-## Creating a diagnostics file in Docker Desktop Enterprise
-
-Select **Diagnose and Feedback** from the Docker menu in the menu bar.
-
-![A diagnostics file is created.](../images/diagnose-mac.png)
-
-Once diagnostics are available, select the **Open** button to display the list of available diagnostics in Finder.
-
-Diagnostics are provided in .zip files identified by date and time. The uncompressed contents are also visible in the Finder window. Send your diagnostics file to your administrator for assistance.
-
-### Creating a diagnostics file from a terminal
-
-In some cases, it is useful to run diagnostics yourself, for instance if Docker Desktop Enterprise cannot start.
-
-To run diagnostics from a terminal, enter the following command:
-
-```
-/Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather
-```
-
-This command displays the information that it is gathering, and when it finishes, it displays information resembling the following example:
-
-```
-Diagnostics Bundle: /tmp/2A989798-1658-4BF0-934D-AC4F148D0782/20190115142942.zip
-Diagnostics ID:     2A989798-1658-4BF0-934D-AC4F148D0782/20190115142942
-```
-
-The name of the diagnostics file is displayed next to “Diagnostics Bundle” (`/tmp/2A989798-1658-4BF0-934D-AC4F148D0782/20190115142942.zip` in this example). This is the file that you attach to the support ticket.
-
-You can view the content of your diagnostics file using the **open** command and specifying the name of your diagnostics file:
-
-```sh
-$ open /tmp/2A989798-1658-4BF0-934D-AC4F148D0782/20190115142942.zip
-```
-
-### Viewing logs in a terminal
-
-In addition to using the **Diagnose and Feedback** option to generate a diagnostics file, you can
-browse Docker Desktop Enterprise logs in a terminal or with the Console app.
-
-To watch the live flow of Docker Desktop Enterprise logs at the command line, run the following command from
-your favorite shell:
-
-```bash
-$ pred='process matches ".*(ocker|vpnkit).*"
-  || (process in {"taskgated-helper", "launchservicesd", "kernel"} && eventMessage contains[c] "docker")'
-$ /usr/bin/log stream --style syslog --level=debug --color=always --predicate "$pred"
-```
-
-Alternatively, to collect the last day of logs (`1d`) in a file, run:
-
-```
-$ /usr/bin/log show --debug --info --style syslog --last 1d --predicate "$pred" >/tmp/logs.txt
-```
-
-### Viewing logs with the Console app
-
-The Console log viewer is located in `/Applications/Utilities`; you can search for it with Spotlight Search.
-
-In the Console window search bar, type
-`docker` and press Enter. Then select **ANY** to expand the drop-down list next to your 'docker' search entry, and select **Process**.
-
-![Mac Console search for Docker app](../images/console.png)
-
-You can use the Console app to search logs, filter the results in various
-ways, and create reports.
-
-### Additional Docker Desktop Enterprise troubleshooting topics
-
-You can also find additional information about various troubleshooting topics in the [Docker Desktop for Mac community](../../../docker-for-mac/troubleshoot.md) documentation.

desktop/enterprise/troubleshoot/windows-issues.md

@@ -1,43 +0,0 @@
----
-title: Troubleshoot Docker Desktop Enterprise issues on Windows
-description: Learn about Docker Desktop Enterprise
-keywords: Docker EE, Windows, Docker Desktop, Enterprise, troubleshoot
-redirect_from:
-- /ee/desktop/troubleshoot/windows-issues/
----
-
-This page contains information on how to diagnose Docker Desktop Enterprise (DDE) issues on Windows.
-
-## Creating a diagnostics file in Docker Desktop Enterprise
-
-Right-click the Docker icon in the system tray and select **Diagnose and Feedback** from the menu. When the **Diagnose & Feedback** window opens, it starts collecting diagnostics.
-
-![A diagnostics file is created.](../images/diagnose-windows.png)
-
-When the log capture is complete, select **You can find diagnostics here**. The file explorer window displays the path to the diagnostics .zip file and allows you to view the contents. Diagnostics are provided in .zip files identified by date and time.
-
-Send your diagnostics file to your administrator for assistance.
-
-### Creating a diagnostics file from a terminal
-
-In some cases, it is useful to run diagnostics yourself, for instance if
-Docker Desktop Enterprise cannot start.
-
-To run diagnostics from a terminal, enter the following command from a powershell window:
-
-```powershell
-'C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe' gather
-```
-
-This command displays the information that it is gathering, and when it finishes, it displays information resembling the following example:
-
-```powershell
-Diagnostics Bundle: C:\Users\djs\AppData\Local\Temp\6CE654F6-7B17-4FC7-AAE0-CC53B73B76A2\20190115163621.zip
-Diagnostics ID: 6CE654F6-7B17-4FC7-AAE0-CC53B73B76A2/20190115163621
-```
-
-The name of the diagnostics file is displayed next to “Diagnostics Bundle”  (`\Temp\6CE654F6-7B17-4FC7-AAE0-CC53B73B76A2\20190115163621.zip` in this example). This is the file that you attach to the support ticket.
-
-### Additional Docker Desktop Enterprise troubleshooting topics
-
-You can also find additional information about various troubleshooting topics in the [Docker Desktop for Windows community](../../../docker-for-windows/troubleshoot.md) documentation.

desktop/enterprise/user/mac-user.md

@@ -1,424 +0,0 @@
----
-title: Use Docker Desktop Enterprise on Mac
-keywords: Docker EE, Windows, Mac, Docker Desktop, Enterprise
-redirect_from:
-- /ee/desktop/user/mac-user/
----
-
-This page contains information about testing the installation and configuring Docker Desktop Enterprise (DDE) runtime options on Mac.
-
-## Test your installation
-
-1. Open a command-line terminal and test that your installation works by
-    running the simple Docker image, [hello-world](https://hub.docker.com/_/hello-world/).
-
-    ```shell
-    $ docker run hello-world
-
-    Unable to find image 'hello-world:latest' locally
-    latest: Pulling from library/hello-world
-    ca4f61b1923c: Pull complete
-    Digest: sha256:ca0eeb6fb05351dfc8759c20733c91def84cb8007aa89a5bf606bc8b315b9fc7
-    Status: Downloaded newer image for hello-world:latest
-
-    Hello from Docker!
-    This message shows that your installation appears to be working correctly.
-    ...
-    ```
-
-2. Start a Dockerized web server. Like the `hello-world` image above, if the
-    image is not found locally, Docker pulls it from Docker Hub.
-
-   ```bash
-    $ docker run --detach --publish=80:80 --name=webserver nginx
-    ```
-
-3. In a web browser, go to `http://localhost/` to view the nginx homepage.
-    Because we specified the default HTTP port, it isn't necessary to append
-    `:80` at the end of the URL.
-
-    ![nginx home page](../images/hello-world-nginx.png)
-
-4. View the details on the container while your web server is running (with
-    `docker container ls` or `docker ps`):
-
-    ```none
-    $ docker container ls
-    CONTAINER ID   IMAGE   COMMAND                  CREATED              STATUS              PORTS                         NAMES
-    56f433965490   nginx   "nginx -g 'daemon off"   About a minute ago   Up About a minute   0.0.0.0:80->80/tcp, 443/tcp   webserver
-    ```
-
-5. Stop and remove containers and images with the following commands. Use the
-    "all" flag (`--all` or `-a`) to view stopped containers.
-
- ```shell
-$ docker container ls
-$ docker container stop webserver
-$ docker container ls -a
-$ docker container rm webserver
-$ docker image ls
-$ docker image rm nginx
-```
-
-## Docker Desktop user interface
-
-The Docker Desktop Enterprise user interface provides options to configure Docker Desktop preferences such as installation, version packs, Docker Hub login, and more. Right-click the Docker icon from the menu bar to open the Docker Desktop user interface.
-
-### Version Selection
-
-The **Version Selection** option lists the version packs installed on your Docker Desktop environment and allows you to switch between Docker Engine and Kubernetes versions using a single click. When you select a different version pack, Docker Desktop restarts and the selected versions of Docker Engine and Kubernetes will be used.
-
-To switch to a different version pack, simply click on the version pack you would like to use.
-
-### Preferences
-
-Click on the Docker icon from the menu bar and then **Preferences** to configure the runtime options described below.
-
-> **Note:** Administrators have the ability to lock some configuration options. Locked options cannot be selected, and are displayed with a lock icon.
-
-![Docker context menu](../images/prefs.png)
-
-#### General
-
-![Preferences](../images/./prefs-general.png)
-
-General settings include:
-
-- **Start Docker Desktop when you log in:** Starts Docker Desktop when you open your session. (Enabled by default)
-
-- **Include VM in Time Machine backups:** Backs up the Docker Desktop Enterprise virtual machine. (Disabled by default)
-
-   **Securely store Docker logins in macOS keychain:** Stores your Docker login
-  credentials. (Enabled by default)
-
-- **Send usage statistics:** Sends diagnostics, crash reports, and usage
-  data to Docker. This information helps Docker improve the application and get
-  more context for troubleshooting problems. (Enabled by default)
-
-#### File Sharing
-
-Choose which local directories to share with your containers. File sharing is
-required for volume mounting if the project lives outside of the `/Users`
-directory. In that case, share the drive where the Dockerfile and volume are
-located. Otherwise, you get `file not found` or `cannot start service` errors at
-runtime.
-
-![File Sharing](../images/prefs-fileshare.png)
-
-File sharing settings include the following options:
-
-- **Add a Directory**: Click `+` and navigate to the directory you want to add.
-
-- **Apply & Restart** makes the directory available to containers using Docker's
-  bind mount (`-v`) feature.
-
-  There are some limitations on the directories that can be shared:
-
-  - They cannot be a subdirectory of a directory that has been shared already.
-  - They cannot already exist inside of Docker.
-
-For more information, see:
-
-- [Volume mounting requires file sharing for any project directories outside of `/Users`](../../../docker-for-mac/troubleshoot.md#volume-mounting-requires-file-sharing-for-any-project-directories-outside-of-users).
-
-#### Disk
-
-Specify the **Disk image location** of the Linux volume, where containers and
-images are stored.
-
-You can also move the disk image location. If you attempt to move the disk image
-to a location that already has one, you get a prompt asking if you want to use
-the existing image or replace it.
-
-![Disk settings](../images/prefs-disk.png)
-
-#### Advanced
-
-On the Advanced tab, you can limit resources available to Docker.
-
-![Advanced Preference settings](../images/prefs-advanced.png)
-
-Advanced settings include the following options:
-
-- **CPUs**: By default, Docker Desktop Enterprise is set to use half the number of processors
-available on the host machine. To increase processing power, set this to a
-higher number; to decrease, lower the number.
-
-- **Memory**: By default, Docker Desktop Enterprise is set to use 2 GB runtime memory,
-allocated from the total available memory on your Mac. To increase RAM, set this
-to a higher number; to decrease it, lower the number.
-
-- **Swap**: Configure swap file size as needed. The default is 1 GB.
-
-#### Proxies
-
-Docker Desktop Enterprise detects HTTP/HTTPS Proxy Settings from macOS and automatically
-propagates these to Docker and to your containers. For example, if you set your
-proxy settings to `http://proxy.example.com`, Docker uses this proxy when
-pulling containers.
-
-![Proxies settings](../images/prefs-proxies.png)
-
-![macOS Proxy Settings](../images/proxy-settings.png)
-
-When you start a container, your proxy settings propagate into the containers.
-For example:
-
-```
-$ docker run -it alpine env
-PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-HOSTNAME=b7edf988b2b5
-TERM=xterm
-HOME=/root
-HTTP_PROXY=http://proxy.example.com:3128
-http_proxy=http://proxy.example.com:3128
-no_proxy=*.local, 169.254/16
-```
-
-You can see from the above output that the `HTTP_PROXY`, `http_proxy`, and
-`no_proxy` environment variables are set. When your proxy configuration changes,
-Docker restarts automatically to pick up the new settings. If you have
-containers that you wish to keep running across restarts, you should consider
-using [restart policies](/engine/reference/run/#restart-policies---restart).
-
-#### Daemon
-
-You can configure options on the Docker daemon that determine how your
-containers run.
-
-Select **Basic** to configure the daemon with interactive settings, or select
-**Advanced** to edit the JSON file directly.
-
-![Daemon](../images/prefs-daemon-basic.png)
-
-##### Experimental features
-
-Docker Desktop Enterprise has experimental features enabled
-on Docker Engine, as described in [Docker Experimental Features](https://github.com/docker/cli/blob/master/experimental/README.md) Readme. If you don't select **Experimental Features**, Docker Desktop Enterprise uses the current generally available release of Docker Engine.
-
-> {% include experimental.md %}
-
-You can see whether you are running experimental mode at the command line. If
-`Experimental` is `true`, then Docker is running in experimental mode, as shown
-here. (If `false`, Experimental mode is off.)
-
-```bash
-{% raw %}$ docker version -f {{.Server.Experimental}}{% endraw %}
-true
-```
-
-##### Insecure registries
-
-You can set up a custom and insecure [registry](../../../registry/introduction.md)
-to store your public or private images (instead of using [Docker Hub](https://hub.docker.com/).
-Add URLs for your insecure registries and registry mirrors on which to host your
-images.
-
-For more information, see:
-
-- [How do I add custom CA certificates?](../../../docker-for-mac/faqs.md#how-do-i-add-custom-ca-certificates)
-
-- [How do I add client certificates?](../../../docker-for-mac/faqs.md#how-do-i-add-client-certificates)
-
-##### Daemon configuration file
-
-Click the **Advanced** tab to configure the daemon from the JSON file. For a
-full list of options, see the Docker Engine [dockerd command line reference](/engine/reference/commandline/dockerd/).
-
-Click **Apply & Restart** to save your settings and reboot Docker. To cancel
-changes, click another preference tab, then choose to discard or not apply
-changes when prompted.
-
-![Docker Daemon](../images/prefs-daemon-adv.png)
-
-#### Kubernetes
-
-Docker Desktop Enterprise includes a standalone Kubernetes server that runs on your Mac, so
-that you can test deploying your Docker workloads on Kubernetes.
-
-The Kubernetes client command, `kubectl`, is included and configured to connect
-to the local Kubernetes server. If you have `kubectl` already installed and
-pointing to some other environment, such as `minikube` or a GKE cluster, be sure
-to change context so that `kubectl` is pointing to `docker-desktop`:
-
-```bash
-$ kubectl config get-contexts
-$ kubectl config use-context docker-desktop
-```
-
-If you installed `kubectl` with Homebrew, or by some other method, and
-experience conflicts, remove `/usr/local/bin/kubectl`.
-
-To enable Kubernetes support and install a standalone instance of Kubernetes running as a Docker container, select **Enable Kubernetes**, choose the [default orchestrator](../../../docker-for-mac/kubernetes.md#override-the-default-orchestrator) and click the **Apply** button.
-
-![Enable Kubernetes](../images/prefs-kubernetes.png)
-
-Images required to run the Kubernetes server are downloaded and instantiated as containers, and the `/usr/local/bin/kubectl` command is installed on your Mac.
-
-When Kubernetes is enabled and running, an additional status bar item displays at the bottom right of the Docker Desktop Enterprise **Preferences** dialog.
-
-![Installation complete](../images/kubernetes-install-complete.png)
-
-The status of Kubernetes shows in the Docker menu and the context points to `docker-desktop`.
-
-![Docker Menu with Kubernetes](../images/kube-context.png)
-
-By default, Kubernetes containers are hidden from commands like `docker
-  service ls`, because managing them manually is not supported. To view these containers, select **Show system containers (advanced)** and click **Apply and restart**. Most users do not have to use this option.
-
-To disable Kubernetes support at any time, clear the **Enable Kubernetes** check box. The
-Kubernetes containers are stopped and removed, and the
-`/usr/local/bin/kubectl` command is removed.
-
-For more information about using the Kubernetes integration with Docker Desktop Enterprise, see [Deploy on Kubernetes](../../../docker-for-mac/kubernetes.md).
-
-#### Reset
-
-Click on the Docker icon from the menu bar and then **Preferences**. Click **Reset** to reset to factory defaults, restart the Docker daemon, reset Kubernetes cluster, or to reset the disk image.
-
-![Uninstall or reset Docker](../images/prefs-reset-mac.png)
-
-### Troubleshoot
-
-The **Diagnose and Feedback** option allows you troubleshoot any issues you may be experiencing with Docker Desktop Enterprise. For more information, see [Troubleshoot DDE issues on Mac](../troubleshoot/mac-issues.md).
-
-### Design new application
-
-Select this option to open the Application Designer user interface. Application Designer provides a library of application and service templates to help Docker developers quickly create new Docker applications. For more information, see [Application Designer](../app-designer.md).
-
-### Docker Hub
-
-Select **Sign in /Create Docker ID** from the Docker Desktop Enterprise menu to access your [Docker Hub](https://hub.docker.com/) account. Once logged in, select **Repositories**  on the Docker Desktop Enterprise menu to access your Docker Hub repositories directly.
-
-See the following [Docker Hub topics](../../../docker-hub/index.md) to learn more:
-
-- [Organizations and Teams in Docker Hub](../../../docker-hub/orgs.md)
-
-- [Builds and Images](../../../docker-hub/official_images.md)
-
-### Add TLS certificates
-
-You can add trusted Certificate Authorities (CAs) (used to verify registry
-server certificates) and client certificates (used to authenticate to
-registries) to your Docker daemon.
-
-#### Add custom CA certificates (server side)
-
-All trusted CAs (root or intermediate) are supported. Docker Desktop Enterprise creates a
-certificate bundle of all user-trusted CAs based on the Mac Keychain, and
-appends it to Moby trusted certificates. So if an enterprise SSL certificate is
-trusted by the user on the host, it is trusted by Docker Desktop Enterprise.
-
-To manually add a custom, self-signed certificate, start by adding the
-certificate to the macOS keychain, which is picked up by Docker Desktop Enterprise. Here is
-an example.
-
-```bash
-$ sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain ca.crt
-```
-
-If you prefer to add the certificate to your own local keychain only (rather
-than for all users), run this command instead:
-
-```
-$ security add-trusted-cert -d -r trustRoot -k ~/Library/Keychains/login.keychain ca.crt
-```
-
-See also, [Directory structures for
-certificates](#directory-structures-for-certificates).
-
-> **Note:** You need to restart Docker Desktop Enterprise after making any changes to the
-keychain or to the `~/.docker/certs.d` directory in order for the changes to
-take effect.
-
-For a complete explanation of how to do this, see the blog post [Adding
-Self-signed Registry Certs to Docker & Docker Desktop Enterprise](http://container-solutions.com/adding-self-signed-registry-certs-docker-mac/).
-
-#### Add client certificates
-
-You can put your client certificates in
-`~/.docker/certs.d/<MyRegistry>:<Port>/client.cert` and
-`~/.docker/certs.d/<MyRegistry>:<Port>/client.key`.
-
-When the Docker Desktop Enterprise application starts up, it copies the `~/.docker/certs.d`
-folder on your Mac to the `/etc/docker/certs.d` directory on Moby (the Docker
-Desktop Enterprise `xhyve` virtual machine).
-
-> * You need to restart Docker Desktop Enterprise after making any changes to the keychain
->   or to the `~/.docker/certs.d` directory in order for the changes to take
->   effect.
->
-> * The registry cannot be listed as an _insecure registry_ (see [Docker Daemon](#daemon)). Docker Desktop Enterprise ignores certificates listed
->   under insecure registries, and does not send client certificates. Commands
->   like `docker run` that attempt to pull from the registry produce error
->   messages on the command line, as well as on the registry.
-
-#### Directory structures for certificates
-
-If you have this directory structure, you do not need to manually add the CA
-certificate to your macOS system login:
-
-```
-/Users/<user>/.docker/certs.d/
-└── <MyRegistry>:<Port>
-   ├── ca.crt
-   ├── client.cert
-   └── client.key
-```
-
-The following further illustrates and explains a configuration with custom
-certificates:
-
-```
-/etc/docker/certs.d/        <-- Certificate directory
-└── localhost:5000          <-- Hostname:port
-   ├── client.cert          <-- Client certificate
-   ├── client.key           <-- Client key
-   └── ca.crt               <-- Certificate authority that signed
-                                the registry certificate
-```
-
-You can also have this directory structure, as long as the CA certificate is
-also in your keychain.
-
-```
-/Users/<user>/.docker/certs.d/
-└── <MyRegistry>:<Port>
-    ├── client.cert
-    └── client.key
-```
-
-To learn more about how to install a CA root certificate for the registry and
-how to set the client TLS certificate for verification, see [Verify repository client with certificates](../../../engine/security/certificates.md) in the Docker Engine
-topics.
-
-### Install shell completion
-
-Docker Desktop Enterprise comes with scripts to enable completion for `docker` and `docker-compose` commands. The completion scripts may be
-found inside `Docker.app`, in the `Contents/Resources/etc/` directory and can be
-installed both in Bash and Zsh.
-
-#### Bash
-
-Bash has [built-in support for completion](https://www.debian-administration.org/article/316/An_introduction_to_bash_completion_part_1). To activate completion for Docker commands, these files need to be
-copied or symlinked to your `bash_completion.d/` directory. For example, if you have
-installed bash through [Homebrew](https://brew.sh).
-
-```bash
-etc=/Applications/Docker.app/Contents/Resources/etc
-ln -s $etc/docker.bash-completion $(brew --prefix)/etc/bash_completion.d/docker
-ln -s $etc/docker-compose.bash-completion $(brew --prefix)/etc/bash_completion.d/docker-compose
-```
-
-#### Zsh
-
-In Zsh, the [completion
-system](http://zsh.sourceforge.net/Doc/Release/Completion-System.html) takes care of things. To activate completion for Docker commands,
-these files need to be copied or symlinked to your Zsh `site-functions/`
-directory. For example, if you installed Zsh through [Homebrew](https://brew.sh):
-
-```bash
-etc=/Applications/Docker.app/Contents/Resources/etc
-ln -s $etc/docker.zsh-completion /usr/local/share/zsh/site-functions/_docker
-ln -s $etc/docker-compose.zsh-completion /usr/local/share/zsh/site-functions/_docker-compose
-```

desktop/enterprise/user/windows-user.md

@@ -1,495 +0,0 @@
----
-title: Use Docker Desktop Enterprise on Windows
-description: Exploring the Windows user interface
-keywords: Desktop Enterprise, Docker for Windows, Docker Desktop, Enterprise, User guide, user
-redirect_from:
-- /ee/desktop/user/windows-user/
----
-
-This page contains information about testing the installation and configuring Docker Desktop Enterprise (DDE) runtime options on Windows.
-
-## Test your installation
-
-1. Open a terminal window (Command Prompt or PowerShell, _but not_ PowerShell ISE).
-
-2. Run `docker --version` to ensure that you have a supported version of Docker:
-
-3. Pull the [hello-world image](https://hub.docker.com/r/library/hello-world) from Docker Hub and run a container:
-
-    ```shell
-    > docker run hello-world
-
-    docker : Unable to find image 'hello-world:latest' locally
-    ...
-
-    latest:
-    Pulling from library/hello-world
-    ca4f61b1923c:
-    Pulling fs layer
-    ca4f61b1923c:
-    Download complete
-    ca4f61b1923c:
-    Pull complete
-    Digest: sha256:97ce6fa4b6cdc0790cda65fe7290b74cfebd9fa0c9b8c38e979330d547d22ce1
-    Status: Downloaded newer image for hello-world:latest
-
-    Hello from Docker!
-    This message shows that your installation appears to be working correctly.
-    ...
-    ```
-
-4. List the `hello-world` _image_ that was downloaded from Docker Hub:
-
-    ```shell
-    > docker image ls
-    ```
-
-5. List the `hello-world` _container_ (that exited after displaying "Hello from Docker!"):
-
-    ```shell
-    > docker container ls --all
-    ```
-
-6. Explore the Docker help pages by running some help commands:
-
-    ```shell
-    > docker --help
-    > docker container --help
-    > docker container ls --help
-    > docker run --help
-    ```
-
-## Explore the application
-
-In this section, we demonstrate the ease and power of Dockerized applications by
-running something more complex, such as an OS and a webserver.
-
-1. Pull an image of the [Ubuntu OS](https://hub.docker.com/r/_/ubuntu/) and run an interactive terminal inside the spawned container:
-
-    ```shell
-    > docker run --interactive --tty ubuntu bash
-
-    docker : Unable to find image 'ubuntu:latest' locally
-    ...
-
-    latest:
-    Pulling from library/ubuntu
-    22dc81ace0ea:
-    Pulling fs layer
-    1a8b3c87dba3:
-    Pulling fs layer
-    91390a1c435a:
-    Pulling fs layer
-    ...
-    Digest: sha256:e348fbbea0e0a0e73ab0370de151e7800684445c509d46195aef73e090a49bd6
-    Status: Downloaded newer image for ubuntu:latest
-    ```
-
-    > Do not use PowerShell ISE
-    >
-    > Interactive terminals do not work in PowerShell ISE (but they do in PowerShell). See [docker/for-win/issues/223](https://github.com/docker/for-win/issues/223).
-
-2. You are in the container. At the root `#` prompt, check the `hostname` of the container:
-
-    ```shell
-    root@8aea0acb7423:/# hostname
-    8aea0acb7423
-    ```
-
-    Notice that the hostname is assigned as the container ID (and is also used in the prompt).
-
-3. Exit the shell with the `exit` command (which also stops the container):
-
-    ```shell
-    root@8aea0acb7423:/# exit
-    >
-    ```
-
-4. List containers with the `--all` option (because no containers are running).
-
-    The `hello-world` container (randomly named, `relaxed_sammet`) stopped after displaying its message. The `ubuntu` container (randomly named, `laughing_kowalevski`) stopped when you exited the container.
-
-    ```shell
-    > docker container ls --all
-
-    CONTAINER ID    IMAGE          COMMAND     CREATED          STATUS                      PORTS    NAMES
-    8aea0acb7423    ubuntu         "bash"      2 minutes ago    Exited (0) 2 minutes ago             laughing_kowalevski
-    45f77eb48e78    hello-world    "/hello"    3 minutes ago    Exited (0) 3 minutes ago             relaxed_sammet
-    ```
-
-5. Pull and run a Dockerized [nginx](https://hub.docker.com/_/nginx/) web server that we name, `webserver`:
-
-    ```shell
-    > docker run --detach --publish 80:80 --name webserver nginx
-
-    Unable to find image 'nginx:latest' locally
-    latest: Pulling from library/nginx
-
-    fdd5d7827f33: Pull complete
-    a3ed95caeb02: Pull complete
-    716f7a5f3082: Pull complete
-    7b10f03a0309: Pull complete
-    Digest: sha256:f6a001272d5d324c4c9f3f183e1b69e9e0ff12debeb7a092730d638c33e0de3e
-    Status: Downloaded newer image for nginx:latest
-    dfe13c68b3b86f01951af617df02be4897184cbf7a8b4d5caf1c3c5bd3fc267f
-    ```
-
-6. Point your web browser at `http://localhost` to display the nginx start page. (You don't need to append `:80` because you specified the default HTTP port in the `docker` command.)
-
-    ![Run nginx edge](../images/nginx-homepage.png)
-
-7. List only your _running_ containers:
-
-    ```shell
-    > docker container ls
-
-    CONTAINER ID    IMAGE    COMMAND                   CREATED          STATUS          PORTS                 NAMES
-    0e788d8e4dfd    nginx    "nginx -g 'daemon of…"    2 minutes ago    Up 2 minutes    0.0.0.0:80->80/tcp    webserver
-    ```
-
-8. Stop the running nginx container by the name we assigned it, `webserver`:
-
-    ```shell
-    >  docker container stop webserver
-    ```
-
-9. Remove all three containers by their names -- the latter two names will differ for you:
-
-    ```shell
-    > docker container rm webserver laughing_kowalevski relaxed_sammet
-    ```
-
-## Docker Desktop user interface
-
-The Docker Desktop Enterprise user interface provides options to configure Docker Desktop settings such as installation, version packs, Docker Hub login, and more. Right-click the Docker icon in the Notifications area (or System tray) to open the Docker Desktop user interface:
-
- ![Showing hidden apps in the taskbar](../images/whale-icon-systray-hidden.png)
-
-> **Note:** Administrators have the ability to lock some configuration options. Locked options cannot be selected, and are displayed with a lock icon.
-
-### Settings
-
-The **Settings** dialog allows you to configure your Docker Desktop Enterprise settings. The following section explains various configuration options available from the **Settings** dialog.
-
-> **Note:** Administrators have the ability to lock some configuration options. Locked options cannot be selected, and are displayed with a lock icon.
-
- Select **Settings** to open the Settings dialog:
-
- ![Docker Desktop Enterprise popup menu](../images/docker-menu-settings.png)
-
-#### General
-
-On the **General** tab of the Settings dialog, you can configure when to start Docker Desktop.
-
-![Settings](../images/settings-general.png)
-
-- **Start Docker Desktop when you log in** - Automatically start the Docker Desktop application upon Windows system login.
-
-- **Send usage statistics** - By default, Docker Desktop sends diagnostics,
-crash reports, and usage data. This information helps Docker improve and troubleshoot the application. Clear the check box to opt out. Docker might prompt you for more information.
-
-- **Expose daemon on tcp://localhost:2375 without TLS** - Click this option to enable legacy clients to connect to the Docker daemon. You must use this option with caution as exposing the daemon without TLS can result in remote code execution attacks.
-
-#### Shared drives
-
-Share your local drives (volumes) with Docker Desktop, so that they are
-available to your [Linux containers](#switch-between-windows-and-linux-containers).
-
-![Shared drives](../images/settings-shared-drives.png)
-
-Permission for shared drives are tied to the credentials you provide here. If you run `docker` commands under a different username than the one configured here, your containers cannot access the mounted volumes.
-
-To apply shared drives, you are prompted for your Windows system (domain) username and password. You can select an option to have Docker store the credentials so that you don't need to enter them every time.
-
-Tips on shared drives, permissions, and volume mounts:
-
-- Shared drives are only required for mounting volumes in [Linux containers](#switch-between-windows-and-linux-containers), not for Windows containers. For Linux containers, you need to share the drive where the Dockerfile and volume are located. If you get errors such as `file not found` or `cannot start service` you may need to enable shared drives. See [Volume mounting requires shared drives for Linux containers](/docker-for-windows/troubleshoot#volume-mounting-requires-shared-drives-for-linux-containers).
-
-- If possible, avoid volume mounts from the Windows host, and instead mount on
-the Linux VM, or use a [data volume](../../../storage/volumes.md) (named volume) or [data container](../../../storage/volumes.md).
-
-- Docker Desktop sets permissions to read/write/execute for users, groups and others [0777 or a+rwx](http://permissions-calculator.org/decode/0777/).
-This is not configurable. See [Permissions errors on data directories for shared volumes](../../../docker-for-windows/troubleshoot.md#permissions-errors-on-data-directories-for-shared-volumes).
-
-##### Firewall rules for shared drives
-
-Shared drives require port 445 to be open between the host machine and the
-virtual machine that runs Linux containers. Docker detects if port 445 is closed
-and shows the following message when you try to add a shared drive:
-
-![Port 445 blocked](../images/shared-drive-firewall-blocked.png)
-
-To share the drive, allow connections between the Windows host machine and the
-virtual machine in Windows Firewall or your third party firewall software. You
-do not need to open port 445 on any other network.
-
-By default, allow connections to `10.0.75.1` on port 445 (the Windows host) from
-`10.0.75.2` (the virtual machine). If your firewall rules seem correct, you may
-need to toggle or [reinstall the File and Print sharing service on the Hyper-V virtual network card](https://stackoverflow.com/questions/42203488/settings-to-windows-firewall-to-allow-docker-for-windows-to-share-drive/43904051#43904051).
-
-##### Shared drives on demand
-
-You can share a drive "on demand" the first time a particular mount is requested.
-
-If you run a Docker command from a shell with a volume mount (as shown in the
-example below) or kick off a Compose file that includes volume mounts, you get a
-popup asking if you want to share the specified drive.
-
-You can select to **Share it**, in which case it is added your Docker Desktop Enterprise [Shared Drives List](#shared-drives) and available to
-containers. Alternatively, you can opt not to share it by selecting **Cancel**.
-
-![Shared drive on demand](../images/shared-drive-on-demand.png)
-
-#### Advanced
-
-The Linux VM restarts after changing the settings on the **Advanced** tab. This takes a few seconds.
-
-![CPU and Memory settings](../images/settings-advanced.png)
-
-- **CPUs** - Change the number of processors assigned to the Linux VM.
-
-- **Memory** - Change the amount of memory the Docker Desktop Enterprise Linux VM uses.
-
-- **Swap** - Configure the swap file size.
-
-#### Network
-
-You can configure Docker Desktop Enterprise networking to work on a virtual private network (VPN).
-
-![Network settings](../images/settings-network.png)
-
-> **Note:** Administrators have the ability to lock some configuration options. Locked options cannot be selected, and are displayed with a lock icon.
-
-- **Internal Virtual Switch** - You can specify a network address translation (NAT) prefix and subnet mask to enable Internet connectivity.
-
-- **DNS Server** - You can configure the DNS server to use dynamic or static IP addressing.
-
-> **Note**: Some users reported problems connecting to Docker Hub on Docker Desktop Enterprise. This would manifest as an error when trying to run
-> `docker` commands that pull images from Docker Hub that are not already
-> downloaded, such as a first time run of `docker run hello-world`. If you
-> encounter this, reset the DNS server to use the Google DNS fixed address:
-> `8.8.8.8`. For more information, see [Networking issues](../../../docker-for-windows/troubleshoot.md#networking-issues) in Troubleshooting.
-
-Updating these settings requires a reconfiguration and reboot of the Linux VM.
-
-#### Proxies
-
-Docker Desktop Enterprise lets you configure HTTP/HTTPS Proxy Settings and
-automatically propagates these to Docker and to your containers.  For example,
-if you set your proxy settings to `http://proxy.example.com`, Docker uses this
-proxy when pulling containers.
-
-![Proxies](../images/settings-proxies.png)
-
-When you start a container, your proxy settings propagate into the containers. For example:
-
-```ps
-> docker run alpine env
-
-PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-HOSTNAME=b7edf988b2b5
-TERM=xterm
-HOME=/root
-HTTP_PROXY=http://proxy.example.com:3128
-http_proxy=http://proxy.example.com:3128
-no_proxy=*.local, 169.254/16
-```
-
-In the output above, the `HTTP_PROXY`, `http_proxy`, and `no_proxy` environment
-variables are set. When your proxy configuration changes, Docker restarts
-automatically to pick up the new settings. If you have containers that you wish
-to keep running across restarts, you should consider using
-[restart policies](/engine/reference/run/#restart-policies---restart).
-
-#### Daemon
-
-Docker Desktop Enterprise enables you to configure the Docker daemon based on your preferences.
-The **Basic** mode lets you configure the more common daemon options with interactive settings and the **Advanced** mode lets you edit the JSON file directly.
-
-![Docker Daemon](../images/settings-daemon-basic.png)
-
-> **Note:** Administrators have the ability to lock some configuration options. Locked options cannot be selected, and are displayed with a lock icon.
-
-##### Experimental mode
-
-Docker Desktop Enterprise has the experimental version
-of Docker Engine enabled, described in the [Docker Experimental Features](https://github.com/docker/cli/blob/master/experimental/README.md) readme. If you don't select **Experimental Features**, Docker Desktop Enterprise uses the current generally available release of Docker Engine.
-
-> {% include experimental.md %}
-
-Run `docker version` to see if you are in Experimental mode. Experimental mode
-is listed under `Server` data. If `Experimental` is `true`, then Docker is
-running in experimental mode, as shown here:
-
-```shell
-> docker version
-
-Client:
- Version:       18.03.0-ce
- API version:   1.37
- Go version:    go1.9.4
- Git commit:    0520e24
- Built: Wed Mar 21 23:06:28 2018
- OS/Arch:       windows/amd64
- Experimental:  true
- Orchestrator:  swarm
-
-Server:
- Engine:
-  Version:      18.03.0-ce
-  API version:  1.37 (minimum version 1.24)
-  Go version:   go1.9.4
-  Git commit:   0520e24
-  Built:        Wed Mar 21 23:21:06 2018
-  OS/Arch:      windows/amd64
-  Experimental: true
-  ```
-
-##### Insecure registries
-
-You can set up your own [registries](../../../registry/index.md) on the **Basic** Daemon settings.
-
-Normally, you store public or private images in [Docker Hub](https://hub.docker.com/). Here, you
-can use Docker to set up your own [insecure registry](../../../registry/insecure.md).
-Simply add URLs for insecure registries and registry mirrors on which to host your images.
-
-For more information, see:
-
-- [How do I add custom CA certificates?](../../../docker-for-windows/faqs.md#how-do-i-add-custom-ca-certificates)
-
-- [How do I add client certificates?](../../../docker-for-windows/faqs.md#how-do-i-add-client-certificates)
-
-#### Daemon configuration file
-
-The **Advanced** daemon settings provide the original option to directly edit
-the JSON configuration file for the [daemon](/engine/reference/commandline/dockerd/).
-
-> Updating these settings requires a reconfiguration and reboot of the Linux VM.
-
-![Docker Daemon](../images/settings-daemon-advanced.png)
-
-For a full list of options on the Docker daemon, see [daemon](../../../engine/reference/commandline/dockerd/), and also sub-topics:
-
-- [Daemon configuration file](../../../engine/reference/commandline/dockerd/#daemon-configuration-file)
-
-- [Linux configuration file](../../../engine/reference/commandline/dockerd/#linux-configuration-file)
-
-- [Windows configuration file](../../../engine/reference/commandline/dockerd/#windows-configuration-file)
-
-#### Kubernetes
-
-Kubernetes is available on Docker Desktop Enterprise. A standalone Kubernetes server is included that runs on your Windows host, so that you can test deploying your
-Docker workloads on Kubernetes.
-
-![Enable Kubernetes](../images/settings-kubernetes.png)
-
-The Kubernetes client command, `kubectl`, is included and configured to connect
-to the local Kubernetes server. If you have `kubectl` already installed and
-pointing to some other environment, such as `minikube` or a GKE cluster, be sure
-to change context so that `kubectl` is pointing to `docker-desktop`:
-
-```bash
-> kubectl config get-contexts
-> kubectl config use-context docker-desktop
-```
-
-You can also change it through the Docker Desktop Enterprise menu:
-
-![Change Kubernetes Context](../images/docker-menu-context-switch.png)
-
-If you installed `kubectl` by another method, and
-experience conflicts, remove it.
-
-- To enable Kubernetes support and install a standalone instance of Kubernetes
-  running as a Docker container, select **Enable Kubernetes** and click the
-  **Install** button.
-
- Images required to run the Kubernetes server are instantiated as containers, and the `kubectl.exe` command is installed in the path.
-
-- By default, Kubernetes containers are hidden from commands like `docker
-  service ls`, because managing them manually is not supported. To make them
-  visible, select **Show system containers (advanced)** and click **Apply and restart**.
-  Most users do not have to use this option.
-
-- To disable Kubernetes support at any time, deselect **Enable Kubernetes**.
-  The Kubernetes containers are stopped and removed, and the
-  `kubectl` command is removed.
-
-  For more about using the Kubernetes integration with Docker Desktop Enterprise,
-  see [Deploy on Kubernetes](../../../docker-for-windows/kubernetes.md).
-
-#### Reset
-
-On the Reset tab, you can restart Docker or reset its configuration.
-
-![Reset](../images/settings-reset.png)
-
-- **Restart Docker Desktop** - Shuts down and restarts the Docker Desktop application.
-
-- **Reset to factory defaults** - Resets Docker to factory defaults. This is
-  useful in cases where Docker stops working or becomes unresponsive.
-
-### Version Selection
-
-The **Version Selection** option lists the version packs installed on your Docker Desktop environment and allows you to switch between Docker Engine and Kubernetes versions using a single click. When you select a different version pack, Docker Desktop restarts and the selected versions of Docker Engine and Kubernetes will be used.
-
-To switch to a different version pack, simply click on the version pack you would like to use.
-
-![Version Selection](../images/win-ver-select.PNG)
-
-### Troubleshoot
-
-The **Diagnose and Feedback** option allows you troubleshoot any issues you may be experiencing with Docker Desktop Enterprise. For more information, see [Troubleshoot DDE issues on Windows](../troubleshoot/windows-issues.md).
-
-### Switch between Windows and Linux containers
-
-From the Docker Desktop Enterprise menu, you can toggle which daemon (Linux or Windows) the Docker CLI talks to. Select **Switch to Windows containers** to use Windows containers, or select **Switch to Linux containers** to use Linux containers.
-
-![Windows-Linux container types switch](../images/docker-menu-switch.png)
-
-For more information on Windows containers, refer to the following documentation:
-
-- Microsoft documentation on [Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index).
-
-- [Build and Run Your First Windows Server Container](https://www.docker.com/blog/build-your-first-docker-windows-server-container/) (blog post) gives a quick tour of how to build and run native Docker Windows containers on Windows 10 and Windows Server 2016 evaluation releases.
-
-- [Getting Started with Windows Containers (Lab)](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md)
-  shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/)
-  application with Windows containers. The MusicStore is a standard .NET application and, [forked here to use containers](https://github.com/friism/MusicStore), is a good example of a multi-container application.
-
-- To understand how to connect to Windows containers from the local host, see [Limitations of Windows containers for `localhost` and published ports](../../../docker-for-windows/troubleshoot.md#limitations-of-windows-containers-for-localhost-and-published-ports).
-
-The **Settings** dialog changes with Windows containers. When you switch to Windows containers, the **Settings** dialog only shows those tabs that are active and apply to your Windows containers:
-
-- [General](#general)
-
-- [Proxies](#proxies)
-
-- [Daemon](#daemon)
-
-- [Diagnose and Feedback](#diagnose-and-feedback)
-
-- [Reset](#reset)
-
-If you set proxies or daemon configuration in Windows containers mode, these apply only on Windows containers. If you switch back to Linux containers, proxies and daemon configurations return to what you had set for Linux containers. Your Windows container settings are retained and become available again when you switch back.
-
-### Docker Hub
-
-Select **Sign in /Create Docker ID** from the Docker Desktop Enterprise menu to access your [Docker Hub](https://hub.docker.com/) account. Once logged in, select **Repositories**  on the Docker Desktop Enterprise menu to access your Docker Hub repositories directly.
-
-See the following [Docker Hub topics](../../../docker-hub/index.md) to learn more:
-
-- [Organizations and Teams in Docker Hub](../../../docker-hub/orgs.md)
-
-- [Builds and Images](../../../docker-hub/official_images.md)
-
-### Design new application
-
-Select this option to open the Application Designer user interface. Application Designer provides a library of application and service templates to help Docker developers quickly create new Docker applications. For more information, see [Application Designer](/desktop/enterprise/app-designer).
-
-## Adding TLS certificates
-
-You can add trusted **Certificate Authorities (CAs)** to your Docker daemon to verify registry server certificates, and **client certificates**, to authenticate to registries.
-
-For more information, see [How do I add custom CA certificates?](../../../docker-for-windows/faqs.md#how-do-i-add-custom-ca-certificates) and
-and [How do I add client certificates?](../../../docker-for-windows/faqs.md#how-do-i-add-client-certificates) in the FAQs.