diff --git a/desktop-enterprise/desktop-mac/README.md b/desktop-enterprise/desktop-mac/README.md
deleted file mode 100644
index 7ab2786eec..0000000000
--- a/desktop-enterprise/desktop-mac/README.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: "Docker Desktop Enterprise"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - mac
- - windows
-tags:
- - installing # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
-notoc: true
----
-
-Docker Desktop Enterprise documentation for Mac
------------------------------------------------
-
-- [Install Docker Desktop Enterprise](../install-guide/README.md)
-- [Getting started](getting-started/README.md)
-- [Environment configuration file (administrators only)](admin-config/README.md)
-- [Troubleshooting](troubleshooting/README.md)
-- [Frequently asked questions](../faq/faq.md)
-- Docker command line reference
-- Docker Compose documentation
-- Docker Engine documentation
-
diff --git a/desktop-enterprise/desktop-mac/admin-config/README.md b/desktop-enterprise/desktop-mac/admin-config/README.md
deleted file mode 100644
index 652758682b..0000000000
--- a/desktop-enterprise/desktop-mac/admin-config/README.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: "Environment configuration on Mac"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - mac
-tags:
- - installing # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
----
-
-Environment configuration on Mac (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 in, and must remain in, the following location:
-
-When you install Docker Desktop Enterprise, a configuration file with default values is installed in, and must remain in, the following location:
-
-`/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 be set to 1.
-
-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 `admin-settings.json` file. If set to `false`, users without elevated access privileges can change this setting from the UI or by directly editing
- `admin-settings.json`. If this setting is omitted, the default value is `false'???
-
-- `value`: Specifies the value of the parameter. The default value, contained in the initial `admin-settings.json` file that is installed with Docker Desktop Enterprise, is used when first running Docker Desktop Enterprise and after a reset to factory defaults. If this setting is omitted, the default value 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": 1,
-
- "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
- },
- "diskPath": {
- "locked": false,
- "value": null
- },
- "diskSizeMiB": {
- "locked": false,
- "value": 65536
- },
- "filesharingDirectories": {
- "locked":false,
- "value":["/Users", ...]
- }
- "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
- }
- },
-
-}
-```
-
-| Parameter | Description |
-| :--------------------------------- | :--------------------------------- |
-| `configurationFileVersion` | Specifies the version of the configuration file format. |
-| `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. |
-| `diskPath` | **Warning:** Do not lock this parameter as it can potentially break the version pack switch. |
-| `diskSizeMiB` | Specifies the amount of disk storage in MiB (1 MiB = 1048576 bytes) allocated for images and containers. |
-| `filesharingDirectories` | The host folders that users can bind-mount in containers. |
-| `dockerDaemonOptions` | Overrides the options in the linux daemon config file. For more information, see [the Docker engine reference](https://docs.docker.com/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 k8s cluster starts when Docker Desktop Enterprise is started. |
-| `showSystemContainers` | If true, displays k8s 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.) | |
diff --git a/desktop-enterprise/desktop-mac/getting-started/README.md b/desktop-enterprise/desktop-mac/getting-started/README.md
deleted file mode 100644
index 0486f5bd1d..0000000000
--- a/desktop-enterprise/desktop-mac/getting-started/README.md
+++ /dev/null
@@ -1,532 +0,0 @@
----
-title: "Getting started with Docker Desktop Enterprise on Mac"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - mac
-tags:
- - deploy # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
- - management
-notoc: true
----
-
-# Getting started with Docker Desktop Enterprise on Mac
-
-## Explore the application
-
-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/){: target="_blank" class="_"}.
-
- ```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.
-
- 
-
- > Early beta releases used `docker` as the hostname to build the URL. Now,
- > ports are exposed on the private IP addresses of the VM and forwarded to
- > `localhost` with no other host name set.
-
-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
- ```
-
-## Preferences menu
-
-Choose {: .inline} → **Preferences** from the
-menu bar and configure the runtime options described below.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-### General
-
-
-
-General settings are:
-
-- **Start Docker when you log in**: Uncheck this option if you don't want Docker
- to start when you open your session.
-
-- **Automatically check for updates** notifies you when an update is available.
- Click **OK** to accept and install updates (or cancel to keep the current
- version). If you disable this option, you can still find out about updates
- manually by choosing {: .inline} → **Check
- for Updates**.
-
-- **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** — Send 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`.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-File share settings are:
-
-- **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 an already shared directory.
- - They cannot already exist inside of Docker.
-
-For more information, see:
-
-- [Namespaces](https://docs.docker.com/docker-for-mac/osxfs/#namespaces){: target="_blank" class="_"} in the topic on
- [osxfs file system sharing](https://docs.docker.com/docker-for-mac/osxfs/){: target="_blank" class="_"}.
-- [Volume mounting requires file sharing for any project directories outside of
- `/Users`](mactroubleshooting/#volume-mounting-requires-file-sharing-for-any-project-directories-outside-of-users){: target="_blank" class="_"}.
-
-
-### 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.
-
-
-
-
-### Advanced
-
-On the Advanced tab, you can limit resources available to Docker.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-Advanced settings are:
-
-**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.
-
-
-
-
-
-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](https://docs.docker.com/engine/reference/run/#restart-policies---restart){: target="_blank" class="_"}.
-
-
-
-### 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 directly.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-#### Experimental features
-
-Docker Desktop Enterprise has experimental features enabled
-on Docker Engine, as described in [Docker Experimental Features
-README](https://github.com/docker/docker-ce/blob/master/components/cli/experimental/README.md){: target="_blank" class="_"}. If you uncheck **experimental mode**, Docker Desktop Enterprise
-uses the current generally available release of Docker Engine.
-
-> Don't enable experimental features in production
->
->Experimental features are not appropriate for production environments or
->workloads. They are meant to be sandbox experiments for new ideas. Some
->experimental features may become incorporated into upcoming stable releases,
->but others may be modified or pulled from subsequent Edge releases, and never
->released on Stable.
-
-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](https://docs.docker.com/registry/introduction){: target="_blank" class="_"} to store your public or private images (instead of
-using [Docker Hub](https://hub.docker.com/){: target="_blank" class="_"} or
-[Docker Trusted Registry](https://docs.docker.com/ee/dtr/){: target="_blank" class="_"}. Add URLs for
-your insecure registries and registry mirrors on which to host your images.
-
-See also:
-- [How do I add custom CA
- certificates?](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"}
-- [How do I add client
- certificates](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-client-certificates){: target="_blank" class="_"}
-
-#### 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 commandline
-reference](https://docs.docker.com/engine/reference/commandline/dockerd){: target="_blank" class="_"}.
-
-Click **Apply & Restart** to save your settings and reboot Docker. Or, to cancel
-changes, click another preference tab, then choose to discard or not apply
-changes when asked.
-
-
-
-### 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.
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-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-for-desktop`:
-
-```bash
-$ kubectl config get-contexts
-$ kubectl config use-context docker-for-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](https://docs.docker.com/docker-for-mac/kubernetes/#override-the-default-orchestrator){: target="_blank" class="_"}
- and click the **Apply** button.
-
- 
-
-
- An Internet connection is required. 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.
-
- 
-
- The status of Kubernetes shows in the Docker menu and the context points to
- `docker-for-desktop`.
-
- 
-
-- 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 need this option.
-
-- To disable Kubernetes support at any time, deselect **Enable Kubernetes**. The
- Kubernetes containers are stopped and removed, and the
- `/usr/local/bin/kubectl` command is removed.
-
- For more about using the Kubernetes integration with Docker Desktop Enterprise, see
- [Deploy on Kubernetes](https://docs.docker.com/docker-for-mac/kubernetes){: target="_blank" class="_"}.
-
-### Reset
-
-Select {: .inline} -> **Preferences** from the
-menu bar, then click **Reset** to reset factory defaults, restart the Docker
-daemon, or uninstall.
-
-
-
-Reset settings are:
-
-* **Restart** - Select to restart the Docker daemon.
-
-* **Remove all data** - This option removes/resets all Docker data _without_ a
- reset to factory defaults (which would cause you to lose settings).
-
-* **Reset to factory defaults** - Choose this option to reset all options on
- Docker Desktop Enterprise to its initial state, the same as when it was first installed.
-
- * **Uninstall** - Choose this option to remove Docker Desktop Enterprise from your
- system.
-
-> Uninstall Docker Desktop Enterprise from the commandline
->
->To uninstall Docker Desktop Enterprise from a terminal, run: `
->--uninstall`. If your instance is installed in the default location, this
->command provides a clean uninstall:
->
->```shell
->$ /Applications/Docker.app/Contents/MacOS/Docker --uninstall
->Docker is running, exiting...
->Docker uninstalled successfully. You can move the Docker application to the trash.
->```
->You might want to use the command-line uninstall if, for example, you find that
->the app is non-functional, and you cannot uninstall it from the menu.
-
-## Application Designer
-
-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 list of available templates is provided:
-
-
-
-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 then name your application and customize the disk location:
-
-
-
-When you select **Assemble**, your application is created.
-
-
-
-Once assembled, the following screen allows you to run the application.
-Select **Run application** to pull the images and start the containers:
-
-
-
-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.
-
-## 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
-```
-
-Or, 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](macconfig.md#directory-structures-for-certificates){: target="_blank" class="_"}.
-
-> **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/){: target="_blank" class="_"}.
-
-### Add client certificates
-
-You can put your client certificates in
-`~/.docker/certs.d/:/client.cert` and
-`~/.docker/certs.d/:/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 Mac OS system login:
-
-```
-/Users//.docker/certs.d/
-└── :
- ├── 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//.docker/certs.d/
-└── :
- ├── 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](https://docs.docker.com/engine/security/certificates){: target="_blank" class="_"} in the Docker Engine
-topics.
-
-## Install shell completion
-
-Docker Desktop Enterprise comes with scripts to enable completion for the `docker`,
-`docker-machine`, 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){:target="_blank"
-class="_"} To activate completion for Docker commands, these files need to be
-copied or symlinked to your `bash_completion.d/` directory. For example, if you
-installed bash via [Homebrew](http://brew.sh/){:target="_blank"
-class="_"}:
-
-```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-machine.bash-completion $(brew --prefix)/etc/bash_completion.d/docker-machine
-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){:target="_blank"
-class="_"} 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 via [Homebrew](http://brew.sh/){:target="_blank"
-class="_"}:
-
-```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-machine.zsh-completion /usr/local/share/zsh/site-functions/_docker-machine
-ln -s $etc/docker-compose.zsh-completion /usr/local/share/zsh/site-functions/_docker-compose
-```
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignChoose.png b/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignChoose.png
deleted file mode 100644
index cbf989db9a..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignChoose.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignCustom.png b/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignCustom.png
deleted file mode 100644
index 4bdbee312d..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignCustom.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignCustom2.png b/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignCustom2.png
deleted file mode 100644
index d1cc381dfa..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignCustom2.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignRun.png b/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignRun.png
deleted file mode 100644
index c205809937..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignRun.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignStart.png b/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignStart.png
deleted file mode 100644
index c6c5d8eeb3..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignStart.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignTest.png b/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignTest.png
deleted file mode 100644
index 39d8dfc702..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/DesktopAppDesignTest.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/hello-world-nginx.png b/desktop-enterprise/desktop-mac/getting-started/images/hello-world-nginx.png
deleted file mode 100644
index 37b5473a14..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/hello-world-nginx.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/kube-context.png b/desktop-enterprise/desktop-mac/getting-started/images/kube-context.png
deleted file mode 100644
index fc7d995e85..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/kube-context.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/kubernetes-install-complete.png b/desktop-enterprise/desktop-mac/getting-started/images/kubernetes-install-complete.png
deleted file mode 100644
index 90db5136c3..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/kubernetes-install-complete.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-advanced.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-advanced.png
deleted file mode 100644
index eeaa75ab98..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-advanced.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-daemon-adv.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-daemon-adv.png
deleted file mode 100644
index 4b59859f14..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-daemon-adv.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-daemon-basic.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-daemon-basic.png
deleted file mode 100644
index 88b9562632..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-daemon-basic.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-disk.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-disk.png
deleted file mode 100644
index dd83059dcc..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-disk.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-fileshare.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-fileshare.png
deleted file mode 100644
index f7aaa33499..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-fileshare.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-general.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-general.png
deleted file mode 100644
index 46795d3cac..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-general.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-kubernetes.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-kubernetes.png
deleted file mode 100644
index efeb098be2..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-kubernetes.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-proxies.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-proxies.png
deleted file mode 100644
index f89d5e5ff0..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-proxies.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs-reset.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs-reset.png
deleted file mode 100644
index 3028935cad..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs-reset.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/prefs.png b/desktop-enterprise/desktop-mac/getting-started/images/prefs.png
deleted file mode 100644
index cd35272b0d..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/prefs.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/proxy-settings.png b/desktop-enterprise/desktop-mac/getting-started/images/proxy-settings.png
deleted file mode 100644
index bdbbfa48ba..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/proxy-settings.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/sign-in.png b/desktop-enterprise/desktop-mac/getting-started/images/sign-in.png
deleted file mode 100644
index cabf4a0fea..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/sign-in.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/getting-started/images/whale-x.png b/desktop-enterprise/desktop-mac/getting-started/images/whale-x.png
deleted file mode 100644
index 29bd366fb2..0000000000
Binary files a/desktop-enterprise/desktop-mac/getting-started/images/whale-x.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/app-design-choose.png b/desktop-enterprise/desktop-mac/images/app-design-choose.png
deleted file mode 100644
index cbf989db9a..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/app-design-choose.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/app-design-custom.png b/desktop-enterprise/desktop-mac/images/app-design-custom.png
deleted file mode 100644
index 4bdbee312d..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/app-design-custom.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/app-design-custom2.png b/desktop-enterprise/desktop-mac/images/app-design-custom2.png
deleted file mode 100644
index d1cc381dfa..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/app-design-custom2.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/app-design-run.png b/desktop-enterprise/desktop-mac/images/app-design-run.png
deleted file mode 100644
index c205809937..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/app-design-run.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/app-design-start.png b/desktop-enterprise/desktop-mac/images/app-design-start.png
deleted file mode 100644
index c6c5d8eeb3..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/app-design-start.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/app-design-test.png b/desktop-enterprise/desktop-mac/images/app-design-test.png
deleted file mode 100644
index 39d8dfc702..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/app-design-test.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/changelog-placeholder.png b/desktop-enterprise/desktop-mac/images/changelog-placeholder.png
deleted file mode 100644
index a22d6b0964..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/changelog-placeholder.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/console.png b/desktop-enterprise/desktop-mac/images/console.png
deleted file mode 100644
index c85f88ec61..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/console.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/diagnose-feedback-id.png b/desktop-enterprise/desktop-mac/images/diagnose-feedback-id.png
deleted file mode 100644
index 9c5d2e142c..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/diagnose-feedback-id.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/diagnose-feedback.png b/desktop-enterprise/desktop-mac/images/diagnose-feedback.png
deleted file mode 100644
index 8b8a021910..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/diagnose-feedback.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/docker-app-drag.png b/desktop-enterprise/desktop-mac/images/docker-app-drag.png
deleted file mode 100644
index e96305181f..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/docker-app-drag.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/docker-app-in-apps.png b/desktop-enterprise/desktop-mac/images/docker-app-in-apps.png
deleted file mode 100644
index 712600b6dd..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/docker-app-in-apps.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/docker-cloud.png b/desktop-enterprise/desktop-mac/images/docker-cloud.png
deleted file mode 100644
index bec6d7be09..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/docker-cloud.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/docker-for-mac-and-toolbox.png b/desktop-enterprise/desktop-mac/images/docker-for-mac-and-toolbox.png
deleted file mode 100644
index bffa4cc6d9..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/docker-for-mac-and-toolbox.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/docker-for-mac-install.png b/desktop-enterprise/desktop-mac/images/docker-for-mac-install.png
deleted file mode 100644
index 421173d0df..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/docker-for-mac-install.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/docker-store.png b/desktop-enterprise/desktop-mac/images/docker-store.png
deleted file mode 100644
index d9ce059d88..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/docker-store.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/hello-world-nginx.png b/desktop-enterprise/desktop-mac/images/hello-world-nginx.png
deleted file mode 100644
index 37b5473a14..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/hello-world-nginx.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/issues-template.png b/desktop-enterprise/desktop-mac/images/issues-template.png
deleted file mode 100644
index 6b9aa48cc9..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/issues-template.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/logs.png b/desktop-enterprise/desktop-mac/images/logs.png
deleted file mode 100644
index bc876f9bd4..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/logs.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/mac-install-success-docker-cloud.png b/desktop-enterprise/desktop-mac/images/mac-install-success-docker-cloud.png
deleted file mode 100644
index 6965c492ab..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/mac-install-success-docker-cloud.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/proxy-settings.png b/desktop-enterprise/desktop-mac/images/proxy-settings.png
deleted file mode 100644
index bdbbfa48ba..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/proxy-settings.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/toolbox-install.png b/desktop-enterprise/desktop-mac/images/toolbox-install.png
deleted file mode 100644
index 83226e703b..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/toolbox-install.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/whale-in-menu-bar.png b/desktop-enterprise/desktop-mac/images/whale-in-menu-bar.png
deleted file mode 100644
index a51ab290d1..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/whale-in-menu-bar.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/images/whale-x.png b/desktop-enterprise/desktop-mac/images/whale-x.png
deleted file mode 100644
index 29bd366fb2..0000000000
Binary files a/desktop-enterprise/desktop-mac/images/whale-x.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/README.md b/desktop-enterprise/desktop-mac/troubleshooting/README.md
deleted file mode 100644
index df9f22d910..0000000000
--- a/desktop-enterprise/desktop-mac/troubleshooting/README.md
+++ /dev/null
@@ -1,392 +0,0 @@
----
-title: "Troubleshooting Mac issues"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - mac
-tags:
- - troubleshooting # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
----
-
-# Troubleshooting Docker Desktop Enterprise on Mac
-
-Here is information about how to diagnose and troubleshoot problems, send logs
-and communicate with the Docker Desktop Enterprise team, use our forums and Knowledge Hub,
-browse and log issues on GitHub, and find workarounds for known problems.
-
-## Docker Knowledge Hub
-
-Check out the [Docker Knowledge
-Hub](http://success.docker.com/){:target="_blank"
-class="_"} for knowledge base articles, FAQs, and
-technical support for various subscription levels.
-
-## Diagnose problems, send feedback, and create GitHub issues
-
-### In-app diagnostics
-If you encounter problems for which you do not find solutions in this
-documentation, on [Docker Desktop for Mac issues on
-GitHub](https://github.com/docker/for-mac/issues){:target="_blank"
-class="_"}, or the [Docker for Mac
-forum](https://forums.docker.com/c/docker-for-mac){:target="_blank"
-class="_"}, we can help you troubleshoot
-the log data.
-
-Choose {: .inline} → **Diagnose & Feedback**
-from the menu bar.
-
-
-
-Once the diagnostics are available, you can upload them and obtain a
-**Diagnostic ID**, which must be provided when communicating with the Docker
-team. For more information on our policy regarding personal data you can read
-[how is personal data handled in Docker
-Desktop](https://docs.docker.com/docker-for-mac/faqs/#how-is-personal-data-handled-in-docker-desktop){:target="_blank"
-class="_"}.
-
-
-
-If you click **Report an issue**, this opens [Docker Desktop Enterprise issues on
-GitHub](https://github.com/docker/for-mac/issues/){:target="_blank"
-class="_"} in your web browser in a
-"create new issue" template, to be completed before submission. Do not forget to
-copy/paste your diagnostic ID.
-
-
-
-### Diagnosing from the terminal
-
-On occasions it is useful to run the diagnostics yourself, for instance if
-Docker Desktop Enterprise cannot start.
-
-First locate the `com.docker.diagnose` tool. If you installed Docker Desktop Enterprise in
-the Applications directory, then it is
-`/Applications/Docker.app/Contents/MacOS/com.docker.diagnose`.
-
-Then to create *and upload* diagnostics, run:
-
-```sh
-$ /Applications/Docker.app/Contents/MacOS/com.docker.diagnose gather -upload
-```
-After the diagnostics have finished, you should have the following output,
-containing your diagnostics ID:
-
-```sh
-Diagnostics Bundle: /tmp/B8CF8400-47B3-4068-ADA4-3BBDCE3985D9/20180726143610.zip
-Diagnostics ID: B8CF8400-47B3-4068-ADA4-3BBDCE3985D9/20180726143610 (uploaded)
-```
-
-The diagnostics ID (here B8CF8400-47B3-4068-ADA4-3BBDCE3985D9/20180726143610) is
-composed of your user ID (D1F48686-F045-4708-85E3-0635B729A596) and a timestamp
-(20180525-145051). Be sure to provide us with the full diagnostics ID, not just
-the user ID.
-
-Don't hesitate browsing the content of these diagnostics:
-
-```sh
-$ open /tmp/D1F48686-F045-4708-85E3-0635B729A596/20180525-145051.zip
-```
-
-
-## Check the logs
-
-In addition to using the diagnose and feedback option to submit logs, you can
-browse the logs yourself. The following documentation is about macOS 10.12
-onwards; for older versions, see [older
-documentation](https://docs.docker.com/v17.12/docker-for-mac/troubleshoot/#logs){:target="_blank"
-class="_"}.
-
-#### In a terminal
-
-To watch the live flow of Docker Desktop Enterprise logs at the command line, run this 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:
-
-```
-$ show --debug --info --style syslog --last 1d --predicate "$pred" >/tmp/logs.txt
-```
-
-#### In the Console app
-
-Macs provide a built-in log viewer, named "Console", which you can use to check
-Docker logs.
-
-The Console lives in `/Applications/Utilities`; you can search for it with
-Spotlight Search.
-
-To read the Docker app log messages, in the top left corner of the window, type
-"docker" and press Enter. Then select the "Any" button that appeared on its
-left, and select "Process" instead.
-
-
-
-You can use the Console Log Query to search logs, filter the results in various
-ways, and create reports.
-
-
-
-## Troubleshooting topics
-
-### Make sure certificates are set up correctly
-
-Docker Desktop Enterprise ignores certificates listed under insecure registries, and does
-not send client certificates to them. Commands like `docker run` that attempt to
-pull from the registry produces error messages on the command line, like this:
-
-```
-Error response from daemon: Get http://192.168.203.139:5858/v2/: malformed HTTP response "\x15\x03\x01\x00\x02\x02"
-```
-
-As well as on the registry. For example:
-
-```
-2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52882: tls: client didn't provide a certificate
-2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52883: tls: first record does not look like a TLS handshake
-```
-
-For more about using client and server side certificates, see [Adding TLS
-certificates](macconfig.md#add-tls-certificates){:target="_blank"
-class="_"} in the Getting Started topic.
-
-### Docker Desktop Enterprise does not start if Mac user account and home folder are renamed after installing the app
-
-See [Do I need to reinstall Docker Desktop Enterprise if I change the name of my macOS
-account?](https://docs.docker.com/docker-for-mac/faqs/#do-i-need-to-reinstall-docker-for-mac-if-i-change-the-name-of-my-macos-account){:target="_blank"
-class="_"}
-in the FAQs.
-
-### Volume mounting requires file sharing for any project directories outside of `/Users`
-
-If you are using mounted volumes and get runtime errors indicating an
-application file is not found, access to a volume mount is denied, or a service
-cannot start, such as when using [Docker Compose](https://docs.docker.com/compose/gettingstarted){:target="_blank"
-class="_"},
-you might need to enable [file sharing](macconfig/#file-sharing){:target="_blank"
-class="_"}.
-
-Volume mounting requires shared drives for projects that live outside of the
-`/Users` directory. Go to {: .inline} →
-**Preferences** → **File sharing** and share the drive that contains the
-Dockerfile and volume.
-
-### Incompatible CPU detected
-
-Docker Desktop Enterprise requires a processor (CPU) that supports virtualization and, more
-specifically, the [Apple Hypervisor
-framework](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/){:target="_blank"
-class="_"}.
-Docker Desktop Enterprise is only compatible with Macs that have a CPU that supports the
-Hypervisor framework. Most Macs built in 2010 and later support it, as described
-in the Apple Hypervisor Framework documentation about supported hardware:
-
-*Generally, machines with an Intel VT-x feature set that includes Extended Page
-Tables (EPT) and Unrestricted Mode are supported.*
-
-To check if your Mac supports the Hypervisor framework, run this command in a
-terminal window.
-
-```bash
-sysctl kern.hv_support
-```
-
-If your Mac supports the Hypervisor Framework, the command prints
-`kern.hv_support: 1`.
-
-If not, the command prints `kern.hv_support: 0`.
-
-See also, [Hypervisor Framework
-Reference](https://developer.apple.com/library/mac/documentation/DriversKernelHardware/Reference/Hypervisor/){:target="_blank"
-class="_"}
-in the Apple documentation, and Docker Desktop Enterprise [System Requirements](install.md){:target="_blank"
-class="_"}.
-
-
-### Workarounds for common problems
-
-* If Docker Desktop Enterprise fails to install or start properly:
-
- * Make sure you quit Docker Desktop Enterprise before installing a new version of the
- application ({: .inline} → **Quit
- Docker**). Otherwise, you get an "application in use" error when you try to
- copy the new app from the `.dmg` to `/Applications`.
-
- * Restart your Mac to stop / discard any vestige of the daemon running from
- the previously installed version.
-
- * Run the uninstall commands from the menu.
-
-
-* If `docker` commands aren't working properly or as expected, you may need to
- unset some environment variables, to make sure you are not using the legacy
- Docker Machine environment in your shell or command window. Unset the
- `DOCKER_HOST` environment variable and related variables.
-
- * If you use bash, use the following command: `unset ${!DOCKER_*}`
-
- * For other shells, unset each environment variable individually as described
- in [Setting up to run Docker Desktop for
- Mac](https://docs.docker.com/docker-for-mac/docker-toolbox/#setting-up-to-run-docker-desktop-for-mac){:target="_blank"
-class="_"} in [Docker Desktop for Mac
- vs. Docker Toolbox](https://docs.docker.com/docker-for-mac/docker-toolbox){:target="_blank"
-class="_"}.
-
-
-* Network connections fail if the macOS Firewall is set to "Block all incoming
- connections". You can enable the firewall, but `bootpd` must be allowed
- incoming connections so that the VM can get an IP address.
-
-
-* For the `hello-world-nginx` example, Docker Desktop Enterprise must be running to get to
- the webserver on `http://localhost/`. Make sure that the Docker whale is
- showing in the menu bar, and that you run the Docker commands in a shell that
- is connected to the Docker Desktop Enterprise Engine (not Engine from Toolbox).
- Otherwise, you might start the webserver container but get a "web page not
- available" error when you go to `localhost`. For more on distinguishing
- between the two environments, see [Docker Desktop for Mac vs. Docker
- Toolbox](https://docs.docker.com/docker-for-mac/docker-toolbox){:target="_blank"
-class="_"}.
-
-
-
-* If you see errors like `Bind for 0.0.0.0:8080 failed: port is already
- allocated` or `listen tcp:0.0.0.0:8080: bind: address is already in use`:
-
- * These errors are often caused by some other software on the Mac using those
- ports.
-
- * Run `lsof -i tcp:8080` to discover the name and pid of the other process and
- decide whether to shut the other process down, or to use a different port in
- your docker app.
-
-## Known issues
-
-* IPv6 is not (yet) supported on Docker Desktop Enterprise.
-
- A workaround is provided that auto-filters out the IPv6 addresses in DNS
- server lists and enables successful network access. For example,
- `2001:4860:4860::8888` would become `8.8.8.8`. To learn more, see these
- issues on GitHub and Docker Desktop for Mac forums:
-
- * [Network timeout when top two DNS servers in /etc/resolv.conf are IPv6
- addresses](https://github.com/docker/for-mac/issues/9){:target="_blank"
-class="_"}
-
- * [ERROR: Network timed out while trying to connect to
- index.docker.io](https://forums.docker.com/t/error-network-timed-out-while-trying-to-connect-to-index-docker-io/17206){:target="_blank"
-class="_"}
-
-
-
-* You might encounter errors when using `docker-compose up` with Docker Desktop Enterprise
- (`ValueError: Extra Data`). We've identified this is likely related to data
- and/or events being passed all at once rather than one by one, so sometimes
- the data comes back as 2+ objects concatenated and causes an error.
-
-* Force-ejecting the `.dmg` after running `Docker.app` from it can cause the
- whale icon to become unresponsive, Docker tasks to show as not responding in
- the Activity Monitor, and for some processes to consume a large amount of CPU
- resources. Reboot and restart Docker to resolve these issues.
-
-* Docker does not auto-start on login even when it is enabled in {: .inline} → **Preferences**. This is related to a
- set of issues with Docker helper, registration, and versioning.
-
-
-
-* Docker Desktop Enterprise uses the [`HyperKit` hypervisor]
- (https://github.com/docker/hyperkit){:target="_blank"
-class="_"} in macOS 10.10 Yosemite and higher. If
- you are developing with tools that have conflicts with `HyperKit`, such as
- [Intel Hardware Accelerated Execution Manager
- (HAXM)](https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager/){:target="_blank"
-class="_"},
- the current workaround is not to run them at the same time. You can pause
- `HyperKit` by quitting Docker Desktop Enterprise temporarily while you work with HAXM.
- This allows you to continue work with the other tools and prevent `HyperKit`
- from interfering.
-
-
-* If you are working with applications like [Apache
- Maven](https://maven.apache.org/){:target="_blank"
-class="_"} that expect settings for `DOCKER_HOST` and
- `DOCKER_CERT_PATH` environment variables, specify these to connect to Docker
- instances through Unix sockets. For example:
-
- ```bash
- export DOCKER_HOST=unix:///var/run/docker.sock
- ```
-
-* `docker-compose` 1.7.1 performs DNS unnecessary lookups for
- `localunixsocket.local` which can take 5s to timeout on some networks. If
- `docker-compose` commands seem very slow but seem to speed up when the network
- is disabled, try appending `127.0.0.1 localunixsocket.local` to the file
- `/etc/hosts`. Alternatively you could create a plain-text TCP proxy on
- localhost:1234 using:
-
- ```
- docker run -d -v /var/run/docker.sock:/var/run/docker.sock -p 127.0.0.1:1234:1234 bobrik/socat TCP-LISTEN:1234,fork UNIX-CONNECT:/var/run/docker.sock
- ```
-
- and then `export DOCKER_HOST=tcp://localhost:1234`.
-
-
-
-
-* There are a number of issues with the performance of directories bind-mounted
- with `osxfs`. In particular, writes of small blocks, and traversals of large
- directories are currently slow. Additionally, containers that perform large
- numbers of directory operations, such as repeated scans of large directory
- trees, may suffer from poor performance. Applications that behave in this way
- include:
-
- - `rake`
- - `ember build`
- - Symfony
- - Magento
- - Zend Framework
- - PHP applications that use [Composer](https://getcomposer.org){:target="_blank"
-class="_"} to install
- dependencies in a ```vendor``` folder
-
- As a work-around for this behavior, you can put vendor or third-party library
- directories in Docker volumes, perform temporary file system operations
- outside of `osxfs` mounts, and use third-party tools like Unison or `rsync` to
- synchronize between container directories and bind-mounted directories. We are
- actively working on `osxfs` performance using a number of different
- techniques. To learn more, see the topic on [Performance issues, solutions,
- and roadmap](https://docs.docker.com/docker-for-mac/osxfs/#performance-issues-solutions-and-roadmap){:target="_blank"
-class="_"}.
-
-* If your system does not have access to an NTP server, then after a hibernate
- the time seen by Docker Desktop Enterprise may be considerably out of sync with the host.
- Furthermore, the time may slowly drift out of sync during use. To manually
- reset the time after hibernation, run:
-
- ```bash
- docker run --rm --privileged alpine hwclock -s
- ```
-
- Or, to resolve both issues, you can add the local clock as a low-priority
- (high stratum) fallback NTP time source for the host. To do this, edit the
- host's `/etc/ntp-restrict.conf` to add:
-
- ```
- server 127.127.1.1 # LCL, local clock
- fudge 127.127.1.1 stratum 12 # increase stratum
- ```
-
- Then restart the NTP service with:
-
- ```bash
- sudo launchctl unload /System/Library/LaunchDaemons/org.ntp.ntpd.plist
- sudo launchctl load /System/Library/LaunchDaemons/org.ntp.ntpd.plist
- ```
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignChoose.png b/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignChoose.png
deleted file mode 100644
index cbf989db9a..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignChoose.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignCustom.png b/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignCustom.png
deleted file mode 100644
index 4bdbee312d..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignCustom.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignCustom2.png b/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignCustom2.png
deleted file mode 100644
index d1cc381dfa..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignCustom2.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignRun.png b/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignRun.png
deleted file mode 100644
index c205809937..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignRun.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignStart.png b/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignStart.png
deleted file mode 100644
index c6c5d8eeb3..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignStart.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignTest.png b/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignTest.png
deleted file mode 100644
index 39d8dfc702..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/DesktopAppDesignTest.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/console.png b/desktop-enterprise/desktop-mac/troubleshooting/images/console.png
deleted file mode 100644
index c85f88ec61..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/console.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/diagnose-feedback-id.png b/desktop-enterprise/desktop-mac/troubleshooting/images/diagnose-feedback-id.png
deleted file mode 100644
index 9c5d2e142c..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/diagnose-feedback-id.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/diagnose-feedback.png b/desktop-enterprise/desktop-mac/troubleshooting/images/diagnose-feedback.png
deleted file mode 100644
index 8b8a021910..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/diagnose-feedback.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/issues-template.png b/desktop-enterprise/desktop-mac/troubleshooting/images/issues-template.png
deleted file mode 100644
index 6b9aa48cc9..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/issues-template.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-mac/troubleshooting/images/whale-x.png b/desktop-enterprise/desktop-mac/troubleshooting/images/whale-x.png
deleted file mode 100644
index 29bd366fb2..0000000000
Binary files a/desktop-enterprise/desktop-mac/troubleshooting/images/whale-x.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/README.md b/desktop-enterprise/desktop-windows/README.md
deleted file mode 100644
index 9c968071fd..0000000000
--- a/desktop-enterprise/desktop-windows/README.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: "Docker Desktop Enterprise"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - mac
- - windows
-tags:
- - installing # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
-notoc: true
----
-
-Docker Desktop Enterprise documentation for Windows
----------------------------------------------------
-
-- [Install Docker Desktop Enterprise](../install-guide/install.md)
- - [Getting started](getting-started/README.md)
- - [Environment configuration file (administrators only)](admin-config/README.md)
- - [Troubleshooting](troubleshooting/README.md)
-- [Frequently asked questions](../faq/faq.md)
-- Docker command line reference
-- Docker Compose documentation
-- Docker Engine documentation
diff --git a/desktop-enterprise/desktop-windows/admin-config/README.md b/desktop-enterprise/desktop-windows/admin-config/README.md
deleted file mode 100644
index 5472e5dd1c..0000000000
--- a/desktop-enterprise/desktop-windows/admin-config/README.md
+++ /dev/null
@@ -1,169 +0,0 @@
----
-title: "Post-installation"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - windows
-tags:
- - installing # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
----
-
-Environment configuration on Windows (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 in, and must remain in, the following location:
-
-`\%ProgramData%\\DockerDesktop\\admin-settings.json`
-
-which defaults to
-
-`C:\\ProgramData\\DockerDesktop\\admin-settings.json`
-
-To edit `admin-settings.json`, you must have administrator 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 be set to 1.
-
-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 `admin-settings.json` file. If set to `false`, users without elevated access privileges can change this setting from the UI or by directly editing
- `admin-settings.json`. If this setting is omitted, the default value is `false'???
-
-- `value`: Specifies the value of the parameter. The default value, contained in the initial `admin-settings.json` file that is installed with Docker Desktop Enterprise, is used when first running Docker Desktop Enterprise and after a reset to factory defaults. If this setting is omitted, the default value 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": 1,
- "engine": {
- "locked": false,
- "value": "linux"
- },
- "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
- },
- "diskPath": {
- "locked": false,
- "value": null
- },
- "diskSizeMiB": {
- "locked": false,
- "value": 64000000000
- },
- "hypervCIDR": {
- "locked": false,
- "value": "192.168.65.0/24"
- },
- "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
- }
- },
-
- "sharedDrives": {
- "locked": false,
- "value": [ "C", "D" ]
- }
-}
-```
-
-| 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. |
-| `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. |
-| `diskPath` | **Warning:** Do not lock this parameter as it can potentially break the version pack switch. |
-| `diskSizeMiB` | Specifies the amount of disk storage in MiB (1 MiB = 1048576 bytes) allocated for images and containers. |
-| `hypervCIDR` | Specifies the subnet used for both Hyper-V 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 [the Docker engine reference](https://docs.docker.com/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 [the Docker engine reference](https://docs.docker.com/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 k8s cluster starts when Docker Desktop Enterprise is started. |
-| `showSystemContainers` | If true, displays k8s 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.) | |
-| `sharedDrives` | Locks the drives users are allowed to share, but does not actually share drives by default (sharing a drive prompts the user for a password). `value` is a whitelist of drives that can be shared. |
diff --git a/desktop-enterprise/desktop-windows/getting-started/README.md b/desktop-enterprise/desktop-windows/getting-started/README.md
deleted file mode 100644
index 7f2c95c027..0000000000
--- a/desktop-enterprise/desktop-windows/getting-started/README.md
+++ /dev/null
@@ -1,602 +0,0 @@
----
-title: "Getting started with Docker Desktop Enterprise on Windows"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - windows
-tags:
- - deploy # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
- - management
----
-
-# Getting started with Docker Desktop Enterprise 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:
-
- ```shell
- > docker --version
-
- Docker version 18.03.0-ce, build 0520e24
- ```
-
-3. Pull the [hello-world image](https://hub.docker.com/r/library/hello-world/){: target="_blank" class="_"} 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/){: target="_blank" class="_"} 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){: target="_blank" class="_"}.
-
-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/){: target="_blank" class="_"} 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.)
-
- 
-
-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 Enterprise Settings menu
-
-The Docker Desktop Enterprise **Settings** menu provides options for configuring
-Docker settings -- installation, updates, version channels, Docker Hub login,
-and more.
-
-This section explains the configuration options accessible from the **Settings** dialog.
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-1. Open Docker Desktop Enterprise by right-clicking the Docker icon in the Notifications area (or System tray):
-
- 
-
-2. Select **Settings...** to open the Settings dialog:
-
- 
-
-### General
-
-On the **General** tab of the Settings dialog, you can configure when to start and update Docker.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-* **Start Docker when you log in** - Automatically start the Docker Desktop Enterprise
-application upon Windows system login.
-
-* **Automatically check for updates** - By default, Docker Desktop Enterprise
-automatically checks for updates and notifies you when an update is available.
-Click **OK** to accept and install updates (or cancel to keep the current
-version). You can manually update by choosing **Check for Updates** from the
-main Docker menu.
-
-* **Send usage statistics** - By default, Docker Desktop Enterprise sends diagnostics,
-crash reports, and usage data. This information helps Docker improve and
-troubleshoot the application. Uncheck to opt out. Docker may also sometimes
-prompt you for more information.
-
-### Shared drives
-
-Share your local drives (volumes) with Docker Desktop Enterprise, so that they are
-available to your [Linux containers](#switch-between-windows-and-linux-containers).
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-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](windowstroubleshooting.md#volume-mounting-requires-shared-drives-for-linux-containers){: target="_blank" class="_"}.
->
- * If possible, avoid volume mounts from the Windows host, and instead mount on
- the Linux VM, or use a [data volume](https://docs.docker.com/storage/volumes/){: target="_blank" class="_"}
- (named volume) or [data container](https://docs.docker.com/storage/volumes/){: target="_blank" class="_"}.
- There are a number of issues with using host-mounted volumes and network paths
- for database files. See [Volume mounts from host paths use a nobrl option to override database locking](windowstroubleshooting.md#volume-mounts-from-host-paths-use-a-nobrl-option-to-override-database-locking){: target="_blank" class="_"}.
->
- * Docker Desktop Enterprise sets permissions to read/write/execute for users, groups and others [0777 or a+rwx](http://permissions-calculator.org/decode/0777/){: target="_blank" class="_"}.
- This is not configurable. See [Permissions errors on data directories for shared volumes](windowstroubleshooting.md#permissions-errors-on-data-directories-for-shared-volumes){: target="_blank" class="_"}.
->
- * Ensure the domain user has access to shared drives, as described in [Verify domain user has permissions for shared drives](windowstroubleshooting.md#verify-domain-user-has-permissions-for-shared-drives-volumes){: target="_blank" class="_"}.
->
- * You can share local drives with your _containers_ but not with Docker Machine
-nodes. See the FAQ, [Can I share local drives and filesystem with my Docker Machine VMs?](https://docs.docker.com/docker-for-windows/faqs/#can-i-share-local-drives-and-filesystem-with-my-docker-machine-vms){: target="_blank" class="_"}.
->
-
-#### 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:
-
-
-
-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](http://stackoverflow.com/questions/42203488/settings-to-windows-firewall-to-allow-docker-for-windows-to-share-drive/43904051#43904051){: target="_blank" class="_"}
-
-#### 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**.
-
-
-
-### Advanced
-
-The Linux VM restarts after changing the settings on the **Advanced** tab. This takes a few seconds.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-* **CPUs** - Change the number of processors assigned to the Linux VM.
-
-* **Memory** - Change the amount of memory the Docker Desktop Enterprise Linux VM uses.
-
-### Network
-
-You can configure Docker Desktop Enterprise networking to work on a virtual private network (VPN).
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-* **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](windowstroubleshooting.md#networking-issues){: target="_blank" class="_"} 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.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-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](https://docs.docker.com/engine/reference/run/#restart-policies---restart){: target="_blank" class="_"}.
-
-
-
-### Daemon
-
-You can configure the Docker daemon to hone how your containers run.
-**Advanced mode** lets you edit the JSON directly. **Basic mode** lets you
-configure the more common daemon options with interactive settings (and also JSON).
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-#### Experimental mode
-
-Docker Desktop Enterprise has the experimental version
-of Docker Engine enabled, described in the [Docker Experimental Features README](https://github.com/docker/cli/blob/master/experimental/README.md){: target="_blank" class="_"} on
-GitHub.
-
-Experimental features are not appropriate for production environments or
-workloads. They are meant to be sandbox experiments for new ideas. Some
-experimental features may become incorporated into upcoming stable releases, but
-others may be modified or pulled from subsequent Edge releases, and never
-released on Stable.
-
-In Docker Desktop Enterprise, you can toggle **experimental mode** on and
-off. If you toggle it off, Docker Desktop Enterprise uses the current generally
-available release of Docker Engine.
-
-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
-```
-
-#### Custom registries
-
-You can set up your own [registries](https://docs.docker.com/registry/introduction){: target="_blank" class="_"} on the **Basic**
-Daemon settings.
-
-Normally, you store public or private images in [Docker Hub](https://hub.docker.com/){: target="_blank" class="_"}
-and [Docker Trusted Registry](https://docs.docker.com/ee/dtr/){: target="_blank" class="_"}. Here, you
-can use Docker to set up your own [insecure registry](https://docs.docker.com/registry/insecure/){: target="_blank" class="_"}.
-Simply add URLs for insecure registries and registry mirrors on which to host your images.
-
-See [How do I add custom CA certificates?](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"}
-and [How do I add client certificates?](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-client-certificates){: target="_blank" class="_"} in the FAQs.
-
-#### Daemon configuration file
-
-The **Advanced** daemon settings provide the original option to directly edit
-the JSON configuration file for the [daemon](https://docs.docker.com/engine/reference/commandline/dockerd){: target="_blank" class="_"}.
-
-> Updating these settings requires a reconfiguration and reboot of the Linux VM.
-
-
-
-For a full list of options on the Docker daemon, see [daemon](https://docs.docker.com/engine/reference/commandline/dockerd){: target="_blank" class="_"}, and also sub-topics:
-
-* [Daemon configuration file](https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file){: target="_blank" class="_"}
-
-* [Linux configuration file](https://docs.docker.com/engine/reference/commandline/dockerd/#linux-configuration-file){: target="_blank" class="_"}
-
-* [Windows configuration file](https://docs.docker.com/engine/reference/commandline/dockerd/#windows-configuration-file){: target="_blank" class="_"}
-
-### 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.
-
-
-
-**Note**: Administrators have the ability to lock some configuration options. No error message is displayed if you attempt to change the value of a locked configuration option, but the value will remain unchanged.
-
-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-for-desktop`:
-
-```bash
-> kubectl config get-contexts
-> kubectl config use-context docker-for-desktop
-```
-
-You can also change it through the Docker Desktop Enterprise menu:
-
-
-
-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
- **Apply and restart** button.
-
- An Internet connection is required. Images required to run the Kubernetes
- server are downloaded and instantiated as containers, and the
- > `Program Files\Docker\Docker\Resources\bin\kubectl.exe` command is installed.
-
-- 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 need this option.
-
-- To disable Kubernetes support at any time, deselect **Enable Kubernetes**.
- The Kubernetes containers are stopped and removed, and the
- `/usr/local/bin/kubectl` command is removed.
-
- For more about using the Kubernetes integration with Docker Desktop Enterprise,
- see [Deploy on Kubernetes](https://docs.docker.com/docker-for-windows/kubernetes){: target="_blank" class="_"}.
-
-### Reset
-
-On the Reset tab, you can restart Docker or reset its configuration.
-
-
-
-* **Restart Docker** - Shuts down and restarts the Docker application.
-
-* **Reset to factory defaults** - Resets Docker to factory defaults. This is
- useful in cases where Docker stops working or becomes unresponsive.
-
-### Diagnose & feedback
-
-Visit our [Troubleshooting](windowstroubleshooting.md){: target="_blank" class="_"} guide for more details.
-
-Log on to our [Docker Desktop for Windows forum](https://forums.docker.com/c/docker-for-windows){: target="_blank" class="_"} to get help from the community, review current user topics, or join a discussion.
-
-Log on to [Docker Desktop for Windows issues on GitHub](https://github.com/docker/for-win/issues){: target="_blank" class="_"} to review community reported issues.
-
-To give feedback on the documentation or update it yourself, use the **Feedback** options at the bottom of each docs page.
-
-## Application Designer
-
-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 list of available templates is provided:
-
-
-
-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 then name your application and customize the disk location:
-
-
-
-When you select **Assemble**, your application is created.
-
-
-
-Once assembled, the following screen allows you to run the application.
-Select **Run application** to pull the images and start the containers:
-
-
-
-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.
-
-## 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
-(the default).
-
-
-
-For more information on Windows containers, refer to this documentation:
-
-- Microsoft documentation on [Windows containers](https://docs.microsoft.com/en-us/virtualization/windowscontainers/about/index){: target="_blank" class="_"}.
-
-- [Build and Run Your First Windows Server Container (Blog Post)](https://blog.docker.com/2016/09/build-your-first-docker-windows-server-container/){: target="_blank" class="_"}
- 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){: target="_blank" class="_"}
- shows you how to use the [MusicStore](https://github.com/aspnet/MusicStore/blob/master/README.md){: target="_blank" class="_"}
- application with Windows containers. The MusicStore is a standard .NET application and,
- [forked here to use containers](https://github.com/friism/MusicStore){: target="_blank" class="_"}, 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](windowstroubleshooting.md#limitations-of-windows-containers-for-localhost-and-published-ports){: target="_blank" class="_"}
-
-> **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)
- * [Docker daemon](#daemon)
- * [Diagnose and Feedback](#diagnose--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.
->
-
-## Adding TLS certificates
-
-To your Docker daemon, you can add trusted **Certificate Authorities (CAs)**, to verify registry server
-certificates, and **client certificates**, to authenticate to registries.
-
-See [How do I add custom CA certificates?](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"}
-and [How do I add client certificates?](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-client-certificates){: target="_blank" class="_"}
-in the FAQs.
-
-## Docker Hub
-
-Select **Sign in /Create Docker ID** from the Docker Desktop Enterprise menu to access your [Docker Hub](https://hub.docker.com/){: target="_blank" class="_"} account. Once logged in, you can access your Docker Hub repositories directly from the Docker Desktop Enterprise menu.
-
-See these [Docker Hub topics](https://docs.docker.com/docker-hub/){: target="_blank" class="_"} to learn more:
-
-* [Organizations and Teams in Docker Hub](https://docs.docker.com/docker-hub/orgs/){: target="_blank" class="_"}
-* [Builds and Images](https://docs.docker.com/docker-hub/official_images/){: target="_blank" class="_"}
-
-## Where to go next
-
-* Try out the walkthrough at [Orientation and setup](https://docs.docker.com/get-started/){: target="_blank" class="_"}.
-
-* Dig in deeper with [Docker Labs](https://github.com/docker/labs/){: target="_blank" class="_"} example walkthroughs and source code.
-
-* Refer to the [Docker CLI Reference Guide](https://docs.docker.com/develop/sdk/){: target="_blank" class="_"}.
-
-* Refer to [Troubleshooting Docker Desktop Enterprise on Windows](windowstroubleshooting.md){: target="_blank" class="_"} if you experience problems.
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignChoose.png b/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignChoose.png
deleted file mode 100644
index cbf989db9a..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignChoose.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignCustom.png b/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignCustom.png
deleted file mode 100644
index 4bdbee312d..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignCustom.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignCustom2.png b/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignCustom2.png
deleted file mode 100644
index d1cc381dfa..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignCustom2.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignRun.png b/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignRun.png
deleted file mode 100644
index c205809937..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignRun.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignStart.png b/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignStart.png
deleted file mode 100644
index c6c5d8eeb3..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignStart.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignTest.png b/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignTest.png
deleted file mode 100644
index 39d8dfc702..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/DesktopAppDesignTest.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/docker-app-search.png b/desktop-enterprise/desktop-windows/getting-started/images/docker-app-search.png
deleted file mode 100644
index 24ec95c12d..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/docker-app-search.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/docker-app-welcome.png b/desktop-enterprise/desktop-windows/getting-started/images/docker-app-welcome.png
deleted file mode 100644
index 786f4cc521..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/docker-app-welcome.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-context-switch.png b/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-context-switch.png
deleted file mode 100644
index f243e02cc5..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-context-switch.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-settings.png b/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-settings.png
deleted file mode 100644
index 12ec3f2ba0..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-settings.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-switch.png b/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-switch.png
deleted file mode 100644
index d5766c5296..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/docker-menu-switch.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/nginx-homepage.png b/desktop-enterprise/desktop-windows/getting-started/images/nginx-homepage.png
deleted file mode 100644
index b0517443a7..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/nginx-homepage.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-advanced.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-advanced.png
deleted file mode 100644
index b8e1b63add..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-advanced.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-daemon-advanced.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-daemon-advanced.png
deleted file mode 100644
index 6ad98a29f6..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-daemon-advanced.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-daemon-basic.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-daemon-basic.png
deleted file mode 100644
index 75cf762f0a..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-daemon-basic.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-general.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-general.png
deleted file mode 100644
index 80b4c86eea..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-general.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-kubernetes.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-kubernetes.png
deleted file mode 100644
index 80285a50fd..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-kubernetes.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-network.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-network.png
deleted file mode 100644
index 0d5477e55d..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-network.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-proxies.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-proxies.png
deleted file mode 100644
index d404ae3c9e..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-proxies.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-reset.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-reset.png
deleted file mode 100644
index 18c5b5ecc6..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-reset.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/settings-shared-drives.png b/desktop-enterprise/desktop-windows/getting-started/images/settings-shared-drives.png
deleted file mode 100644
index 4550899d2c..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/settings-shared-drives.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/shared-drive-firewall-blocked.png b/desktop-enterprise/desktop-windows/getting-started/images/shared-drive-firewall-blocked.png
deleted file mode 100644
index b504831dd4..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/shared-drive-firewall-blocked.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/shared-drive-on-demand.png b/desktop-enterprise/desktop-windows/getting-started/images/shared-drive-on-demand.png
deleted file mode 100644
index 37dceed10b..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/shared-drive-on-demand.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/whale-icon-systray-hidden.png b/desktop-enterprise/desktop-windows/getting-started/images/whale-icon-systray-hidden.png
deleted file mode 100644
index 8f8b5bd05b..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/whale-icon-systray-hidden.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/getting-started/images/whale-icon-systray.png b/desktop-enterprise/desktop-windows/getting-started/images/whale-icon-systray.png
deleted file mode 100644
index d4c6cc532b..0000000000
Binary files a/desktop-enterprise/desktop-windows/getting-started/images/whale-icon-systray.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/app-design-choose.png b/desktop-enterprise/desktop-windows/images/app-design-choose.png
deleted file mode 100644
index cbf989db9a..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/app-design-choose.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/app-design-custom.png b/desktop-enterprise/desktop-windows/images/app-design-custom.png
deleted file mode 100644
index 4bdbee312d..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/app-design-custom.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/app-design-custom2.png b/desktop-enterprise/desktop-windows/images/app-design-custom2.png
deleted file mode 100644
index d1cc381dfa..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/app-design-custom2.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/app-design-run.png b/desktop-enterprise/desktop-windows/images/app-design-run.png
deleted file mode 100644
index c205809937..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/app-design-run.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/app-design-start.png b/desktop-enterprise/desktop-windows/images/app-design-start.png
deleted file mode 100644
index c6c5d8eeb3..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/app-design-start.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/app-design-test.png b/desktop-enterprise/desktop-windows/images/app-design-test.png
deleted file mode 100644
index 39d8dfc702..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/app-design-test.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/diagnose-feedback.png b/desktop-enterprise/desktop-windows/images/diagnose-feedback.png
deleted file mode 100644
index b3b7b0a039..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/diagnose-feedback.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/diagnostic-id.png b/desktop-enterprise/desktop-windows/images/diagnostic-id.png
deleted file mode 100644
index c5ec51c099..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/diagnostic-id.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/docker-app-search.png b/desktop-enterprise/desktop-windows/images/docker-app-search.png
deleted file mode 100644
index 24ec95c12d..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/docker-app-search.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/docker-app-welcome.png b/desktop-enterprise/desktop-windows/images/docker-app-welcome.png
deleted file mode 100644
index 786f4cc521..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/docker-app-welcome.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/docker-menu-context-switch.png b/desktop-enterprise/desktop-windows/images/docker-menu-context-switch.png
deleted file mode 100644
index f243e02cc5..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/docker-menu-context-switch.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/docker-menu-settings.png b/desktop-enterprise/desktop-windows/images/docker-menu-settings.png
deleted file mode 100644
index 12ec3f2ba0..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/docker-menu-settings.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/docker-menu-switch.png b/desktop-enterprise/desktop-windows/images/docker-menu-switch.png
deleted file mode 100644
index d5766c5296..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/docker-menu-switch.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/hyperv-enabled.png b/desktop-enterprise/desktop-windows/images/hyperv-enabled.png
deleted file mode 100644
index 3d4002ffc1..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/hyperv-enabled.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/hyperv-manager.png b/desktop-enterprise/desktop-windows/images/hyperv-manager.png
deleted file mode 100644
index 384782726b..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/hyperv-manager.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/issue-template.png b/desktop-enterprise/desktop-windows/images/issue-template.png
deleted file mode 100644
index 8f9daa0908..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/issue-template.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/nginx-homepage.png b/desktop-enterprise/desktop-windows/images/nginx-homepage.png
deleted file mode 100644
index b0517443a7..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/nginx-homepage.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-advanced.png b/desktop-enterprise/desktop-windows/images/settings-advanced.png
deleted file mode 100644
index b8e1b63add..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-advanced.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-daemon-advanced.png b/desktop-enterprise/desktop-windows/images/settings-daemon-advanced.png
deleted file mode 100644
index 6ad98a29f6..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-daemon-advanced.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-daemon-basic.png b/desktop-enterprise/desktop-windows/images/settings-daemon-basic.png
deleted file mode 100644
index 75cf762f0a..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-daemon-basic.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-general.png b/desktop-enterprise/desktop-windows/images/settings-general.png
deleted file mode 100644
index 80b4c86eea..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-general.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-kubernetes.png b/desktop-enterprise/desktop-windows/images/settings-kubernetes.png
deleted file mode 100644
index 80285a50fd..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-kubernetes.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-network.png b/desktop-enterprise/desktop-windows/images/settings-network.png
deleted file mode 100644
index 0d5477e55d..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-network.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-proxies.png b/desktop-enterprise/desktop-windows/images/settings-proxies.png
deleted file mode 100644
index d404ae3c9e..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-proxies.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-reset.png b/desktop-enterprise/desktop-windows/images/settings-reset.png
deleted file mode 100644
index 18c5b5ecc6..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-reset.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/settings-shared-drives.png b/desktop-enterprise/desktop-windows/images/settings-shared-drives.png
deleted file mode 100644
index 4550899d2c..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/settings-shared-drives.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/shared-drive-firewall-blocked.png b/desktop-enterprise/desktop-windows/images/shared-drive-firewall-blocked.png
deleted file mode 100644
index b504831dd4..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/shared-drive-firewall-blocked.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/shared-drive-on-demand.png b/desktop-enterprise/desktop-windows/images/shared-drive-on-demand.png
deleted file mode 100644
index 37dceed10b..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/shared-drive-on-demand.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/virtualization-enabled.png b/desktop-enterprise/desktop-windows/images/virtualization-enabled.png
deleted file mode 100644
index e7dd271e15..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/virtualization-enabled.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/whale-icon-systray-hidden.png b/desktop-enterprise/desktop-windows/images/whale-icon-systray-hidden.png
deleted file mode 100644
index 8f8b5bd05b..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/whale-icon-systray-hidden.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/whale-icon-systray.png b/desktop-enterprise/desktop-windows/images/whale-icon-systray.png
deleted file mode 100644
index d4c6cc532b..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/whale-icon-systray.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/images/whale-x.png b/desktop-enterprise/desktop-windows/images/whale-x.png
deleted file mode 100644
index c8f930330f..0000000000
Binary files a/desktop-enterprise/desktop-windows/images/whale-x.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/README.md b/desktop-enterprise/desktop-windows/troubleshooting/README.md
deleted file mode 100644
index 1bb9c62e21..0000000000
--- a/desktop-enterprise/desktop-windows/troubleshooting/README.md
+++ /dev/null
@@ -1,620 +0,0 @@
----
-title: "Troubleshooting Windows issues"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - windows
-tags:
- - troubleshooting # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
----
-
-# Troubleshooting Docker Desktop Enterprise on Windows
-
-Here is information about how to diagnose and troubleshoot problems, send logs
-and communicate with the Docker Desktop Enterprise team, use our forums and Knowledge
-Hub, browse and log issues on GitHub, and find workarounds for known problems.
-
-## Docker Knowledge Hub
-
-Check out the [Docker Knowledge
-Hub](http://success.docker.com/q){: target="_blank" class="_"} for knowledge base articles, FAQs, and
-technical support for various subscription levels.
-
-## Diagnose problems, send feedack, and create GitHub issues
-
-### In-app diagnostics
-
-If you encounter problems for which you do not find solutions in this
-documentation, on [Docker Desktop for Windows issues on
-GitHub](https://github.com/docker/for-win/issues){: target="_blank" class="_"}, or the [Docker Desktop for Windows
-forum](https://forums.docker.com/c/docker-for-windows){: target="_blank" class="_"}, we can help you
-troubleshoot the log data.
-
-Choose {: .inline} → **Diagnose & Feedback**
-from the menu bar.
-
-
-
-Once the **Diagnose & Feedback** window is opened, it collects
-diagnostics. When the diagnostics are available, you can upload them and obtain a
-**Diagnostic ID**, which must be provided when communicating with the Docker
-team. For more information on our policy regarding personal data you can read
-[how is personal data handled in Docker
-Desktop](https://docs.docker.com/docker-for-mac/faqs/#how-is-personal-data-handled-in-docker-desktop){: target="_blank" class="_"}.
-
-
-
-If you click on **Report an issue**, this opens [Docker Desktop for Windows issues on
-GitHub](https://github.com/docker/for-win/issues/){: target="_blank" class="_"} in your web browser in a
-"create new issue" template, to be completed before submision. Do not forget to
-include your diagnostic ID.
-
-
-
-### Diagnosing from the terminal
-
-On occasions it is useful to run the diagnostics yourself, for instance if
-Docker Desktop Enterprise cannot start.
-
-First locate the `com.docker.diagnose`, that should be in `C:\Program
-Files\Docker\Docker\resources\com.docker.diagnose.exe`.
-
-To create *and upload* diagnostics in Powershell, run:
-
-```powershell
- PS C:\> & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload
-```
-
-After the diagnostics have finished, you should have the following output,
-containing your diagnostic ID:
-
-```sh
-Diagnostics Bundle: C:\Users\User\AppData\Local\Temp\CD6CF862-9CBD-4007-9C2F-5FBE0572BBC2\20180720152545.zip
-Diagnostics ID: CD6CF862-9CBD-4007-9C2F-5FBE0572BBC2/20180720152545 (uploaded)
-```
-
-## Troubleshooting topics
-
-### Make sure certificates are set up correctly
-
-Docker Desktop Enterprise ignores certificates listed under insecure registries, and
-does not send client certificates to them. Commands like `docker run` that
-attempt to pull from the registry produces error messages on the command line,
-like this:
-
-```
-Error response from daemon: Get http://192.168.203.139:5858/v2/: malformed HTTP response "\x15\x03\x01\x00\x02\x02"
-```
-
-As well as on the registry. For example:
-
-```
-2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52882: tls: client didn't provide a certificate
-2017/06/20 18:15:30 http: TLS handshake error from 192.168.203.139:52883: tls: first record does not look like a TLS handshake
-```
-
-For more about using client and server side certificates, see [How do I add
-custom CA certificates?](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-custom-ca-certificates){: target="_blank" class="_"} and [How
-do I add client certificates?](https://docs.docker.com/docker-for-windows/faqs/#how-do-i-add-client-certificates){: target="_blank" class="_"} in the
-FAQs topic.
-
-### Volumes
-
-#### Permissions errors on data directories for shared volumes
-
-Docker Desktop Enterprise sets permissions on [shared volumes](windowsconfig.md#shared-drives){: target="_blank" class="_"}
-to a default value of [0777](http://permissions-calculator.org/decode/0777/){: target="_blank" class="_"}
-(`read`, `write`, `execute` permissions for `user` and for `group`).
-
-The default permissions on shared volumes are not configurable. If you are
-working with applications that require permissions different from the shared
-volume defaults at container runtime, you need to either use non-host-mounted
-volumes or find a way to make the applications work with the default file
-permissions.
-
-Docker Desktop Enterprise currrently implements host-mounted volumes based on the
-[Microsoft SMB
-protocol](https://msdn.microsoft.com/en-us/library/windows/desktop/aa365233(v=vs.85).aspx){: target="_blank" class="_"},
-which does not support fine-grained, `chmod` control over these permissions.
-
-See also, [Can I change permissions on shared volumes for container-specific
-deployment
-requirements?](https://docs.docker.com/docker-for-windows/faqs/#can-i-change-permissions-on-shared-volumes-for-container-specific-deployment-requirements){: target="_blank" class="_"}
-in the FAQs, and for more of an explanation, the GitHub issue, [Controlling
-Unix-style perms on directories passed through from shared Windows
-drives](https://github.com/docker/docker.github.io/issues/3298){: target="_blank" class="_"}.
-
-#### inotify on shared drives does not work
-
-Currently, `inotify` does not work on Docker Desktop Enterprise. This becomes evident,
-for example, when an application needs to read/write to a container across a
-mounted drive. Instead of relying on filesystem inotify, we recommend using
-polling features for your framework or programming language.
-
-* **Workaround for nodemon and Node.js** - If you are using
- [nodemon](https://github.com/remy/nodemon){: target="_blank" class="_"} with `Node.js`, try the fallback
- polling mode described here: [nodemon isn't restarting node
- applications](https://github.com/remy/nodemon#application-isnt-restarting){: target="_blank" class="_"}
-
-* **Docker Desktop for Windows issue on GitHub** - See the issue [Inotify on shared
- drives does not
- work](https://github.com/docker/for-win/issues/56#issuecomment-242135705){: target="_blank" class="_"}
-
-#### Volume mounting requires shared drives for Linux containers
-
-If you are using mounted volumes and get runtime errors indicating an
-application file is not found, access is denied to a volume mount, or a service
-cannot start, such as when using [Docker Compose](https://docs.docker.com/compose/gettingstarted){: target="_blank" class="_"},
-you might need to enable [shared drives](windowsconfig/#shared-drives){: target="_blank" class="_"}.
-
-Volume mounting requires shared drives for Linux containers (not for Windows
-containers). Go to {: .inline}
-→ **Settings** → **Shared Drives** and share the drive that contains the
-Dockerfile and volume.
-
-#### Verify domain user has permissions for shared drives (volumes)
-
-> **Tip**: Shared drives are only required for volume mounting [Linux
-> containers](windowsconfig/#switch-between-windows-and-linux-containers){: target="_blank" class="_"}, not Windows
-> containers.
-
-Permissions to access shared drives are tied to the username and password you
-use to set up [shared drives](windowsconfig.md#shared-drives){: target="_blank" class="_"}. If you run `docker`
-commands and tasks under a different username than the one used to set up shared
-drives, your containers don't have permissions to access the mounted volumes.
-The volumes show as empty.
-
-The solution to this is to switch to the domain user account and reset
-credentials on shared drives.
-
-Here is an example of how to debug this problem, given a scenario where you
-shared the `C` drive as a local user instead of as the domain user. Assume the
-local user is `samstevens` and the domain user is `merlin`.
-
-1. Make sure you are logged in as the Windows domain user (for our example,
- `merlin`).
-
-2. Run `net share c` to view user permissions for `\, FULL`.
-
- ```
- > net share c
-
- Share name C
- Path C:\
- Remark
- Maximum users No limit
- Users SAMSTEVENS
- Caching Caching disabled
- Permission windowsbox\samstevens, FULL
- ```
-
-3. Run the following command to remove the share.
-
- ```
- > net share c /delete
- ```
-
-4. Re-share the drive via the [Shared Drives dialog](windowsconfig/#shared-drives){: target="_blank" class="_"},
- and provide the Windows domain user account credentials.
-
-5. Re-run `net share c`.
-
- ```
- > net share c
-
- Share name C
- Path C:\
- Remark
- Maximum users No limit
- Users MERLIN
- Caching Caching disabled
- Permission windowsbox\merlin, FULL
- ```
-
-See also, the related issue on GitHub, [Mounted volumes are empty in the
-container](https://github.com/docker/for-win/issues/25){: target="_blank" class="_"}.
-
-#### Volume mounts from host paths use a `nobrl` option to override database locking
-
-You may encounter problems using volume mounts on the host, depending on the
-database software and which options are enabled. Docker Desktop Enterprise uses
-[SMB/CIFS
-protocols](https://msdn.microsoft.com/en-us/library/windows/desktop/aa365233(v=vs.85).aspx){: target="_blank" class="_"}
-to mount host paths, and mounts them with the `nobrl` option, which prevents
-lock requests from being sent to the database server
-([docker/for-win#11](https://github.com/docker/for-win/issues/11){: target="_blank" class="_"},
-[docker/for-win#694](https://github.com/docker/for-win/issues/694){: target="_blank" class="_"}. This is
-done to ensure container access to database files shared from the host. Although
-it solves the over-the-network database access problem, this "unlocked" strategy
-can interfere with other aspects of database functionality (for example,
-write-ahead logging (WAL) with SQLite, as described in
-[docker/for-win#1886](https://github.com/Sonarr/Sonarr/issues/1886){: target="_blank" class="_"}.
-
-If possible, avoid using shared drives for volume mounts on the host with
-network paths, and instead mount on the MobyVM, or create a [data
-volume](https://docs.docker.com/engine/tutorials/dockervolumes/#data-volumes){: target="_blank" class="_"} (named volume) or [data
-container](https://docs.docker.com/engine/tutorials/dockervolumes/#creating-and-mounting-a-data-volume-container){: target="_blank" class="_"}.
-See also, the [volumes key under service
-configuration](https://docs.docker.com/compose/compose-file/#volumes){: target="_blank" class="_"} and the [volume
-configuration
-reference](https://docs.docker.com/compose/compose-file/#volume-configuration-reference){: target="_blank" class="_"} in the
-Compose file documentation.
-
-
-#### Local security policies can block shared drives and cause login errors
-
-You need permissions to mount shared drives to use the Docker for Windows
-[shared drives](windowsconfig/#shared-drives){: target="_blank" class="_"} feature.
-
-If local policy prevents this, you get errors when you attempt to enable shared
-drives on Docker. This is not something Docker can resolve, since you do need
-these permissions to use the feature.
-
-Here are snip-its from example error messages:
-
-```none
-Logon failure: the user has not been granted the requested logon type at
-this computer.
-
-[19:53:26.900][SambaShare ][Error ] Unable to mount C drive: mount
-error(5): I/O error Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
-mount: mounting //10.0.75.1/C on /c failed: Invalid argument
-```
-
-See also, [Docker for
-Windows issue 98](https://github.com/docker/for-win/issues/98){: target="_blank" class="_"}.
-
-#### Understand symlinks limitations
-
-Symlinks work within and across containers. However, symlinks created outside of
-containers (for example, on the host) do not work. To learn more, see [Are
-symlinks supported?](https://docs.docker.com/docker-for-windows/faqs/#are-symlinks-supported){: target="_blank" class="_"} in the FAQs.
-
-#### Avoid unexpected syntax errors, use Unix style line endings for files in containers
-
-Any file destined to run inside a container must use Unix style `\n` line
-endings. This includes files referenced at the command line for builds and in
-RUN commands in Docker files.
-
-Docker containers and `docker build` run in a Unix environment, so files in
-containers must use Unix style line endings: `\n`, _not_ Windows style: `\r\n`.
-Keep this in mind when authoring files such as shell scripts using Windows
-tools, where the default is likely to be Windows style line endings. These
-commands ultimately get passed to Unix commands inside a Unix based container
-(for example, a shell script passed to `/bin/sh`). If Windows style line endings
-are used, `docker run` fails with syntax errors.
-
-For an example of this issue and the resolution, see this issue on GitHub:
-[Docker RUN fails to execute shell
-script](https://github.com/moby/moby/issues/24388){: target="_blank" class="_"}.
-
-### Virtualization
-
-In order for Docker Desktop Enterprise to function properly your machine needs:
-
-1. [Hyper-V](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-technology-overview){: target="_blank" class="_"}
- installed and working
-
-2. Virtualization enabled
-
-
-#### Hyper-V
-
-Docker Desktop Enterprise requires a Hyper-V as well as the Hyper-V Module for Windows
-Powershell to be installed and enabled. The Docker Desktop Enterprise installer enables
-it for you.
-
-See [these
-instructions](https://msdn.microsoft.com/en-us/virtualization/hyperv_on_windows/quick_start/walkthrough_install){: target="_blank" class="_"}
-to install Hyper-V manually. A reboot is *required*. If you install Hyper-V
-without the reboot, Docker Desktop Enterprise does not work correctly. On some systems,
-Virtualization needs to be enabled in the BIOS. The steps to do so are Vendor
-specific, but typically the BIOS option is called `Virtualization Technology
-(VTx)` or similar.
-
-
-From the start menu, type in "Turn Windows features on or off" and hit enter.
-In the subequent screen, verify Hyper-V is enabled and has a checkmark:
-
-
-
-#### Hyper-V driver for Docker Machine
-
-Docker Desktop Enterprise comes with the legacy tool Docker Machine which uses the old
-[`boot2docker.iso`](https://github.com/boot2docker/boot2docker){:
-target="_blank" class="_"}, and the [Microsoft Hyper-V
-driver](https://docs.docker.com/machine/drivers/hyper-v){: target="_blank" class="_"} to create local virtual machines. _This is
-tangential to using Docker for Windows_, but if you want to use Docker Machine
-to create multiple local VMs, or to provision remote machines, see the [Docker
-Machine](https://docs.docker.com/machine/){: target="_blank" class="_"} topics. We mention this here only in case someone is
-looking for information about Docker Machine on Windows, which requires that
-Hyper-V is enabled, an external network switch is active, and referenced in the
-flags for the `docker-machine create` command [as described in the Docker
-Machine driver example](https://docs.docker.com/machine/drivers/hyper-v/#example){: target="_blank" class="_"}.
-
-#### Virtualization must be enabled
-
-In addition to [Hyper-V](#hyper-v), virtualization must be enabled. Check the
-Performance tab on the Task Manager:
-
-{:width="700px"}
-
-If, at some point, if you manually uninstall Hyper-V or disable virtualization,
-Docker for Windows cannot start. See: [Unable to run Docker for Windows on
-Windows 10 Enterprise](https://github.com/docker/for-win/issues/74){: target="_blank" class="_"}.
-
-### Networking and WiFi problems upon Docker Desktop Enterprise install
-
-Some users have encountered networking issues during install and startup of
-Docker Desktop Enterprise. For example, upon install or auto-reboot, network adapters
-and/or WiFi gets disabled. In some scenarios, problems are due to having
-VirtualBox or its network adapters still installed, but in other scenarios this
-is not the case. (See also, Docker Desktop Enterprise issue on GitHub: [Enabling
-Hyper-V feature turns my wi-fi
-off](https://github.com/docker/for-win/issues/139){: target="_blank" class="_"}.)
-
-Here are some steps to take if you encounter similar problems:
-
-1. Ensure **virtualization** is enabled, as described above in [Virtualization
- must be enabled](#virtualization-must-be-enabled).
-
-2. Ensure **Hyper-V** is installed and enabled, as described above in [Hyper-V
- must be enabled](#hyper-v).
-
-3. Ensure **DockerNAT** is enabled by checking the **Virtual Switch Manager**
- on the Actions tab on the right side of the **Hyper-V Manager**.
-
- 
-
-4. Set up an external network switch. If you plan at any point to use [Docker
- Machine](https://docs.docker.com/machine/overview/){: target="_blank" class="_"} to set up multiple local VMs, you need this
- anyway, as described in the topic on the [Hyper-V driver for Docker
- Machine](https://docs.docker.com/machine/drivers/hyper-v/#example){: target="_blank" class="_"}. You can replace `DockerNAT`
- with this switch.
-
-5. If previous steps fail to solve the problems, follow steps on the [Cleanup
- README](https://github.com/Microsoft/Virtualization-Documentation/blob/master/windows-server-container-tools/CleanupContainerHostNetworking/README.md){: target="_blank" class="_"}.
-
- > Read full description before you run Windows cleanup script
- >
- >The cleanup command has two flags, `-Cleanup` and
- >`-ForceDeleteAllSwitches`. Read the whole page before running any scripts,
- >especially warnings about `-ForceDeleteAllSwitches`. {: .warning}
-
-### Windows containers and Windows Server 2016
-
-Docker Desktop Enteprise is not supported on Windows Server 2016, instead you can use
-[Docker Enterprise Basic Edition](https://docs.docker.com/ee/){: target="_blank" class="_"} at no additional cost.
-
-If you have questions about how to run Windows containers on Windows 10, see
-[Switch between Windows and Linux
-containers](windowsconfig/#switch-between-windows-and-linux-containers){: target="_blank" class="_"}.
-
-A full tutorial is available in [docker/labs](https://github.com/docker/labs){: target="_blank" class="_"} at
-[Getting Started with Windows
-Containers](https://github.com/docker/labs/blob/master/windows/windows-containers/README.md){: target="_blank" class="_"}.
-
-You can install a native Windows binary which allows you to develop and run
-Windows containers without Docker Desktop Enterprise. However, if you install Docker
-this way, you cannot develop or run Linux containers. If you try to run a Linux
-container on the native Docker daemon, an error occurs:
-
-```none
-C:\Program Files\Docker\docker.exe:
- image operating system "linux" cannot be used on this platform.
- See 'C:\Program Files\Docker\docker.exe run --help'.
-```
-
-### Limitations of Windows containers for `localhost` and published ports
-
-Docker Desktop Enterprise provides the option to switch Windows and Linux containers.
-If you are using Windows containers, keep in mind that there are some
-limitations with regard to networking due to the current implementation of
-Windows NAT (WinNAT). These limitations may potentially resolve as the Windows
-containers project evolves.
-
-One thing you may encounter rather immediately is that published ports on
-Windows containers do not do loopback to the local host. Instead, container
-endpoints are only reachable from the host using the container's IP and port.
-
-So, in a scenario where you use Docker to pull an image and run a webserver with
-a command like this:
-
-```shell
-> docker run -d -p 80:80 --name webserver nginx
-```
-
-Using `curl http://localhost`, or pointing your web browser at
-`http://localhost` does not display the `nginx` web page (as it would do with
-Linux containers).
-
-To reach a Windows container from the local host, you need to specify the IP
-address and port for the container that is running the service.
-
-You can get the container IP address by using [`docker
-inspect`](https://docs.docker.com/engine/reference/commandline/inspect){: target="_blank" class="_"} with some `--format` options
-and the ID or name of the container. For the example above, the command would
-look like this, using the name we gave to the container (`webserver`) instead of
-the container ID:
-
-{% raw %}
-```bash
-$ docker inspect \
- --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' \
- webserver
-```
-{% endraw %}
-
-This gives you the IP address of the container, for example:
-
-{% raw %}
-```bash
-$ docker inspect \
- --format='{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' \
- webserver
-
-172.17.0.2
-```
-{% endraw %}
-
-Now you can connect to the webserver by using `http://172.17.0.2:80` (or simply
-`http://172.17.0.2`, since port `80` is the default HTTP port.)
-
-For more information, see:
-
-* Docker Desktop for Windows issue on GitHub: [Port binding does not work for
- locahost](https://github.com/docker/for-win/issues/458){: target="_blank" class="_"}
-
-* [Published Ports on Windows Containers Don't Do
- Loopback](https://blog.sixeyed.com/published-ports-on-windows-containers-dont-do-loopback/){: target="_blank" class="_"}
-
-* [Windows NAT capabilities and
- limitations](https://blogs.technet.microsoft.com/virtualization/2016/05/25/windows-nat-winnat-capabilities-and-limitations/){: target="_blank" class="_"}
-
-### Running Docker Desktop Enterprise in nested virtualization scenarios
-
-Docker Desktop Enterprise can run inside a Windows 10 virtual machine (VM) running on
-apps like Parallels or VMware Fusion on a Mac provided that the VM is properly
-configured. However, problems and intermittent failures may still occur due to
-the way these apps virtualize the hardware. For these reasons, _**Docker Desktop Enterprise is not supported for nested virtualization scenarios**_. It might work
-in some cases, and not in others.
-
-The better solution is to run Docker Desktop Enterprise natively on a Windows system
-(to work with Windows or Linux containers), or on Mac to work
-with Linux containers.
-
-#### If you still want to use nested virtualization
-
-* Make sure nested virtualization support is enabled in VMWare or Parallels.
- Check the settings in **Hardware → CPU & Memory → Advanced Options → Enable
- nested virtualization** (the exact menu sequence might vary slightly).
-
-* Configure your VM with at least 2 CPUs and sufficient memory to run your
- workloads.
-
-* Make sure your system is more or less idle.
-
-* Make sure your Windows OS is up-to-date. There have been several issues with
- some insider builds.
-
-* The processor you have may also be relevant. For example, Westmere based Mac
- Pros have some additional hardware virtualization features over Nehalem based
- Mac Pros and so do newer generations of Intel processors.
-
-#### Typical failures we see with nested virtualization
-
-* Slow boot time of the Linux VM. If you look in the logs and find some entries
- prefixed with `Moby`. On real hardware, it takes 5-10 seconds to boot the
- Linux VM; roughly the time between the `Connected` log entry and the `*
- Starting Docker ... [ ok ]` log entry. If you boot the Linux VM inside a
- Windows VM, this may take considerably longer. We have a timeout of 60s or so.
- If the VM hasn't started by that time, we retry. If the retry fails we print
- an error. You can sometimes work around this by providing more resources to
- the Windows VM.
-
-* Sometimes the VM fails to boot when Linux tries to calibrate the time stamp
- counter (TSC). This process is quite timing sensitive and may fail when
- executed inside a VM which itself runs inside a VM. CPU utilization is also
- likely to be higher.
-
-#### Related issues
-
-Discussion thread on GitHub at [Docker Desktop for Windows issue
-267](https://github.com/docker/for-win/issues/267){: target="_blank" class="_"}
-
-### Networking issues
-
-Some users have reported problems connecting to Docker Hub on the Docker Desktop for
-Windows stable version. (See GitHub issue
-[22567](https://github.com/moby/moby/issues/22567){: target="_blank" class="_"}.)
-
-Here is an example command and error message:
-
-```shell
-> docker run hello-world
-
-Unable to find image 'hello-world:latest' locally
-Pulling repository docker.io/library/hello-world
-C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error while pulling image: Get https://index.docker.io/v1/repositories/library/hello-world/images: dial tcp: lookup index.docker.io on 10.0.75.1:53: no such host.
-See 'C:\Program Files\Docker\Docker\Resources\bin\docker.exe run --help'.
-```
-
-As an immediate workaround to this problem, reset the DNS server to use the
-Google DNS fixed address: `8.8.8.8`. You can configure this via the **Settings**
-→ **Network** dialog, as described in the topic [Network](windowsconfig.md#network).
-Docker automatically restarts when you apply this setting, which could take some
-time.
-
-We are currently investigating this issue.
-
-### NAT/IP configuration
-
-By default, Docker Desktop Enterprise uses an internal network prefix of
-`10.0.75.0/24`. Should this clash with your normal network setup, you can change
-the prefix from the **Settings** menu. See the [Network](windowsconfig.md#network){: target="_blank" class="_"} topic
-under [Settings](windowsconfig.md#docker-desktop-enterprise-settings-menu){: target="_blank" class="_"}.
-
-## Workarounds
-
-### `inotify` currently does not work on Docker Desktop Enterprise
-
-If you are using `Node.js` with `nodemon`, a temporary workaround is to try the
-fallback polling mode described here: [nodemon isn't restarting node
-applications](https://github.com/remy/nodemon#application-isnt-restarting){: target="_blank" class="_"}. See
-also this issue on GitHub [Inotify on shared drives does not
-work](https://github.com/docker/for-win/issues/56#issuecomment-242135705){: target="_blank" class="_"}.
-
-### Reboot
-
-Restart your PC to stop / discard any vestige of the daemon running from the
-previously installed version.
-
-### Unset `DOCKER_HOST`
-
-The `DOCKER_HOST` environmental variable does not need to be set. If you use
-bash, use the command `unset ${!DOCKER_*}` to unset it. For other shells,
-consult the shell's documentation.
-
-### Make sure Docker is running for webserver examples
-
-For the `hello-world-nginx` example and others, Docker Desktop Enterprise must be
-running to get to the webserver on `http://localhost/`. Make sure that the
-Docker whale is showing in the menu bar, and that you run the Docker commands in
-a shell that is connected to the Docker for Windows Engine (not Engine from
-Toolbox). Otherwise, you might start the webserver container but get a "web page
-not available" error when you go to `docker`.
-
-### How to solve `port already allocated` errors
-
-If you see errors like `Bind for 0.0.0.0:8080 failed: port is already allocated`
-or `listen tcp:0.0.0.0:8080: bind: address is already in use` ...
-
-These errors are often caused by some other software on Windows using those
-ports. To discover the identity of this software, either use the `resmon.exe`
-GUI and click **Network** and then **Listening Ports** or in a Powershell use
-`netstat -aon | find /i "listening "` to discover the PID of the process
-currently using the port (the PID is the number in the rightmost column). Decide
-whether to shut the other process down, or to use a different port in your
-docker app.
-
-### Docker fails to start when firewall or anti-virus software is installed
-
-**Some firewalls and anti-virus software might be incompatible with Microsoft
-**Windows 10 builds**, such as Windows 10 Anniversary Update. The conflict
-typically occurs after a Windows update or new install of the firewall, and
-manifests as an error response from the Docker daemon and a **Docker Desktop Enterprise
-start failure**. The Comodo Firewall was one example of this problem, but users
-report that software has since been updated to work with these Windows 10
-builds.
-
-See the Comodo forums topics [Comodo Firewall conflict with
-Hyper-V](https://forums.comodo.com/bug-reports-cis/comodo-firewall-began-conflict-with-hyperv-t116351.0.html){: target="_blank" class="_"}
-and [Windows 10 Anniversary build doesn't allow Comodo drivers to be
-installed](https://forums.comodo.com/install-setup-configuration-help-cis/windows-10-aniversary-build-doesnt-allow-comodo-drivers-to-be-installed-t116322.0.html){: target="_blank" class="_"}.
-A Docker Desktop for Windows user-created issue describes the problem specifically as it
-relates to Docker: [Docker fails to start on Windows
-10](https://github.com/docker/for-win/issues/27){: target="_blank" class="_"}.
-
-For a temporary workaround, uninstall the firewall or anti-virus software, or
-explore other workarounds suggested on the forum.
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/images/diagnose-feedback.png b/desktop-enterprise/desktop-windows/troubleshooting/images/diagnose-feedback.png
deleted file mode 100644
index b3b7b0a039..0000000000
Binary files a/desktop-enterprise/desktop-windows/troubleshooting/images/diagnose-feedback.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/images/diagnostic-id.png b/desktop-enterprise/desktop-windows/troubleshooting/images/diagnostic-id.png
deleted file mode 100644
index c5ec51c099..0000000000
Binary files a/desktop-enterprise/desktop-windows/troubleshooting/images/diagnostic-id.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/images/hyperv-enabled.png b/desktop-enterprise/desktop-windows/troubleshooting/images/hyperv-enabled.png
deleted file mode 100644
index 3d4002ffc1..0000000000
Binary files a/desktop-enterprise/desktop-windows/troubleshooting/images/hyperv-enabled.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/images/hyperv-manager.png b/desktop-enterprise/desktop-windows/troubleshooting/images/hyperv-manager.png
deleted file mode 100644
index 384782726b..0000000000
Binary files a/desktop-enterprise/desktop-windows/troubleshooting/images/hyperv-manager.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/images/issue-template.png b/desktop-enterprise/desktop-windows/troubleshooting/images/issue-template.png
deleted file mode 100644
index 8f9daa0908..0000000000
Binary files a/desktop-enterprise/desktop-windows/troubleshooting/images/issue-template.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/images/virtualization-enabled.png b/desktop-enterprise/desktop-windows/troubleshooting/images/virtualization-enabled.png
deleted file mode 100644
index e7dd271e15..0000000000
Binary files a/desktop-enterprise/desktop-windows/troubleshooting/images/virtualization-enabled.png and /dev/null differ
diff --git a/desktop-enterprise/desktop-windows/troubleshooting/images/whale-x.png b/desktop-enterprise/desktop-windows/troubleshooting/images/whale-x.png
deleted file mode 100644
index c8f930330f..0000000000
Binary files a/desktop-enterprise/desktop-windows/troubleshooting/images/whale-x.png and /dev/null differ
diff --git a/desktop-enterprise/faq/README.md b/desktop-enterprise/faq/README.md
deleted file mode 100644
index 7458b6b2dd..0000000000
--- a/desktop-enterprise/faq/README.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: "Docker Desktop Enterprise"
-summary: (concept, reference (CLI), task,)
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - mac
- - windows
-tags:
- - management # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
- - troubleshooting
-notoc: true
----
-
-
-FAQs
-====
-
-- ???
-
--
diff --git a/desktop-enterprise/images/changelog-placeholder.png b/desktop-enterprise/images/changelog-placeholder.png
deleted file mode 100644
index a22d6b0964..0000000000
Binary files a/desktop-enterprise/images/changelog-placeholder.png and /dev/null differ
diff --git a/desktop-enterprise/images/docker-app-drag.png b/desktop-enterprise/images/docker-app-drag.png
deleted file mode 100644
index e96305181f..0000000000
Binary files a/desktop-enterprise/images/docker-app-drag.png and /dev/null differ
diff --git a/desktop-enterprise/images/docker-app-in-apps.png b/desktop-enterprise/images/docker-app-in-apps.png
deleted file mode 100644
index 712600b6dd..0000000000
Binary files a/desktop-enterprise/images/docker-app-in-apps.png and /dev/null differ
diff --git a/desktop-enterprise/images/docker-cloud.png b/desktop-enterprise/images/docker-cloud.png
deleted file mode 100644
index bec6d7be09..0000000000
Binary files a/desktop-enterprise/images/docker-cloud.png and /dev/null differ
diff --git a/desktop-enterprise/images/docker-for-mac-and-toolbox.png b/desktop-enterprise/images/docker-for-mac-and-toolbox.png
deleted file mode 100644
index bffa4cc6d9..0000000000
Binary files a/desktop-enterprise/images/docker-for-mac-and-toolbox.png and /dev/null differ
diff --git a/desktop-enterprise/images/docker-for-mac-install.png b/desktop-enterprise/images/docker-for-mac-install.png
deleted file mode 100644
index 421173d0df..0000000000
Binary files a/desktop-enterprise/images/docker-for-mac-install.png and /dev/null differ
diff --git a/desktop-enterprise/images/docker-store.png b/desktop-enterprise/images/docker-store.png
deleted file mode 100644
index d9ce059d88..0000000000
Binary files a/desktop-enterprise/images/docker-store.png and /dev/null differ
diff --git a/desktop-enterprise/images/logs.png b/desktop-enterprise/images/logs.png
deleted file mode 100644
index bc876f9bd4..0000000000
Binary files a/desktop-enterprise/images/logs.png and /dev/null differ
diff --git a/desktop-enterprise/images/mac-install-success-docker-cloud.png b/desktop-enterprise/images/mac-install-success-docker-cloud.png
deleted file mode 100644
index 6965c492ab..0000000000
Binary files a/desktop-enterprise/images/mac-install-success-docker-cloud.png and /dev/null differ
diff --git a/desktop-enterprise/images/toolbox-install.png b/desktop-enterprise/images/toolbox-install.png
deleted file mode 100644
index 83226e703b..0000000000
Binary files a/desktop-enterprise/images/toolbox-install.png and /dev/null differ
diff --git a/desktop-enterprise/images/whale-in-menu-bar.png b/desktop-enterprise/images/whale-in-menu-bar.png
deleted file mode 100644
index a51ab290d1..0000000000
Binary files a/desktop-enterprise/images/whale-in-menu-bar.png and /dev/null differ
diff --git a/desktop-enterprise/install-guide/README.md b/desktop-enterprise/install-guide/README.md
deleted file mode 100644
index a3aab6d672..0000000000
--- a/desktop-enterprise/install-guide/README.md
+++ /dev/null
@@ -1,174 +0,0 @@
----
-title: "Installation"
-summary: task
-visibleto: employees # logged in with any Docker ID that has @docker.com email as primary email for Docker ID
-author: paige.hargrave
-platform:
- - mac
- - windows
-tags:
- - installing # pick from kbase list: https://github.com/docker/kbase/blob/master/README.md#prerequisites
-notoc: true
----
-
-Install Docker Desktop Enterprise
----------------------------------
-
-## System Requirements
-
-### Windows:
-
-- Windows 10 Pro or Enterprise version 15063.
-
-- Hyper-V and Containers Windows features must be enabled.
-
-- The following hardware prerequisites are required to successfully run Client
-Hyper-V on Windows 10:
-
- - 64 bit processor with [Second Level Address
- Translation (SLAT)](http://en.wikipedia.org/wiki/Second_Level_Address_Translation){: target="_blank" class="_"}
-
- - 4GB system RAM
-
- - BIOS-level hardware virtualization support must be enabled in the
- BIOS settings:
-
-
-
-
-### Mac:
-
-- 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 10.12 and newer macOS releases are supported. We recommend upgrading to the latest 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.
-
-
-> **Warning:** If you are using the community version of Docker Desktop, you must uninstall Docker Desktop community in order to install Docker Desktop Enterprise.
-
-## Installation
-
-Download Docker Desktop Enterprise:
-- [**Windows**](https://download-stage.docker.com/win/enterprise/30183/DockerDesktop.msi)
-
-- [**Mac**](https://download-stage.docker.com/mac/enterprise/30173/Docker.pkg)
-
-What the install includes: Docker Engine, Docker CLI client, and Docker Compose. To install, double-click the .msi or .pkg file and follow the instructions.
-
-
-
-For administrators, the following command line options support fine tuning and mass installation:
-
-`\$ sudo installer -pkg Docker.pkg -target /`
-
-Once installed, run Docker Desktop Enterprise from your Application
-folder.
-
-Administrators can configure additional settings by modifying the administrator configuration file
-as described in the Administrator configuration file section.
-
-### License file
-
-You must have a Docker Desktop Enterprise license file installed in the following location:
-
-`/Library/Application Support/Docker/DockerDesktop/license.json`
-
-If the license file is missing, the following error is displayed when you try to run Docker Desktop Enterprise:
-
-
-
- ### 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 Docker Enterprise 2.0 (Docker
-Engine 17.06.2 / Kubernetes 1.8.11). The following version packs can be
-downloaded and installed if you want to use a different version of the Docker Engine
-and Kubernetes for development work:
-
-- [Docker Community (18.09.0/Kubernetes
- 1.10.3)](https://github.com/docker/pinata/releases/download/2.0.0.0-ent-mac79-enterprise/community.ddvp)
-
-- [Docker Enterprise 2.1 (18.09.0/Kubernetes
- 1.11.2)](https://github.com/docker/pinata/releases/download/2.0.0.0-ent-mac79-enterprise/enterprise-2.1.ddvp)
-
-Version packs are installed manually or, for administrators, by using the version pack status and upgrade tool. Once installed, version packs can be selected for use in the Docker Desktop Enterprise menu.
-
-#### Version pack tool (administrators only)
-
-The administrator version pack tool is a command line executable that provides status and version pack installation and upgrades.
-
-When you install Docker Desktop Enterprise, the tool is installed in the following location:
-
-- Windows:
-
-`\[ApplicationPath\]/dockerdesktop-admin.exe`
-
-- Mac:
-
-`\[ApplicationPath\]/Contents/Resources/bin/desktop-admin`
-
-To run tool commands, you must have elevated access privileges: sudo on macOS,
-administrator on Windows.
-
-
-- **version-pack install**
-Installs or upgrades a version pack to the version contained in the specified `.*ddvp*` archive.
-
- - Windows:
-
-`*desktop-admin -InstallVersionPack=\[path-to-archive\]*`
-
- - Mac:
-
-`desktop-admin version-pack install \[path-to-archive\]`
-
-
-- **version-pack uninstall**
-Uninstalls the specified version pack.
-
- - Windows:
-
-`*desktop-admin -UninstallVersionPack=\[version-pack-name\]*`
-
- - Mac:
-
-`desktop-admin version-pack uninstall \[version-pack-name\]`
-
-
-#### Manual version pack installation and selection
----------------------------------------------------
-Version packs can be installed by double-clicking a .ddvp file
-(with Docker Desktop running).
-
-
-
-Installed version packs are listed in **Version Selection** and are selected using the **Add version pack** menu entry.
-
-
-
-If more than one verson 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 Enterprise restarts and the selected Docker Engine and
-Kubernetes versions are used.
-
-## Where to go next
-
-* [Getting started with Docker Desktop Enterprise](../desktop-windows/getting-started/README.md) on Windows
-
-* [Getting started with Docker Desktop Enterprise](../desktop-mac/getting-started/README.md) on Mac
diff --git a/desktop-enterprise/install-guide/images/DesktopInstall.png b/desktop-enterprise/install-guide/images/DesktopInstall.png
deleted file mode 100644
index fc1018f639..0000000000
Binary files a/desktop-enterprise/install-guide/images/DesktopInstall.png and /dev/null differ
diff --git a/desktop-enterprise/install-guide/images/DesktopInstallLicense.png b/desktop-enterprise/install-guide/images/DesktopInstallLicense.png
deleted file mode 100644
index 06852eb465..0000000000
Binary files a/desktop-enterprise/install-guide/images/DesktopInstallLicense.png and /dev/null differ
diff --git a/desktop-enterprise/install-guide/images/DesktopInstallVersion.png b/desktop-enterprise/install-guide/images/DesktopInstallVersion.png
deleted file mode 100644
index bf598b304a..0000000000
Binary files a/desktop-enterprise/install-guide/images/DesktopInstallVersion.png and /dev/null differ
diff --git a/desktop-enterprise/install-guide/images/DesktopVersionSelect.png b/desktop-enterprise/install-guide/images/DesktopVersionSelect.png
deleted file mode 100644
index a84f2d9eee..0000000000
Binary files a/desktop-enterprise/install-guide/images/DesktopVersionSelect.png and /dev/null differ
diff --git a/desktop-enterprise/install-guide/images/DesktopWindowsPrereq.png b/desktop-enterprise/install-guide/images/DesktopWindowsPrereq.png
deleted file mode 100644
index a75a0b5da5..0000000000
Binary files a/desktop-enterprise/install-guide/images/DesktopWindowsPrereq.png and /dev/null differ