Home Explore Blog CI



docker

2nd chunk of `content/manuals/desktop/setup/vm-vdi.md`
76b9d4937eda4660db0b9c20a1ff21d335047ba325802e940000000100000b60
In the terminal, you will see `Hello from Docker!` if everything is working
correctly.

### View insights and manage Docker Cloud

For insights and management, use the [Docker Cloud
Dashboard](https://app.docker.com/cloud). It provides visibility into your
builds, runs, and cloud resource usage. Key features include:

- Overview: Monitor cloud usage, build cache, and top repositories built.
- Build history: Review past builds with filtering and sorting options.
- Run history: Track container runs and sort by various options.
- Integrations: Learn how to set up cloud builders and runners for your CI
  pipeline.
- Settings: Manage cloud builders, usage, and account settings.

Access the Docker Cloud Dashboard at https://app.docker.com/cloud.

### Limitations

The following limitations apply when using Docker Cloud:

- Persistence: Containers are launched in a cloud engine that remains available
  as long as you interact with and consume the containers' output. After closing
  Docker Desktop, or about 30 minutes of inactivity, the engine is shut down and
  becomes inaccessible, along with any data stored in it, including images,
  containers, and volumes. A new engine is provisioned for any new workloads.
- Usage and billing: During beta, no charges are incurred for using Docker Cloud
  resources. Docker enforces a usage cap and reserves the right to disable
  Docker Cloud access at any time.

## Virtual desktop support when using nested virtualization

> [!NOTE]
>
> Support for running Docker Desktop on a virtual desktop is available to Docker Business customers, on VMware ESXi or Azure VMs only.

Docker support includes installing and running Docker Desktop within the VM, provided that nested virtualization is correctly enabled. The only hypervisors successfully tested are VMware ESXi and Azure, and there is no support for other VMs. For more information on Docker Desktop support, see [Get support](/manuals/desktop/troubleshoot-and-support/support.md).

For troubleshooting problems and intermittent failures that are outside of Docker's control, you should contact your hypervisor vendor. Each hypervisor vendor offers different levels of support. For example, Microsoft supports running nested Hyper-V both on-prem and on Azure, with some version constraints. This may not be the case for VMware ESXi.

Docker does not support running multiple instances of Docker Desktop on the same machine in a VM or VDI environment. 

> [!TIP]
>
> If you're running Docker Desktop inside a Citrix VDI, note that Citrix can be used with a variety of underlying hypervisors, for example VMware, Hyper-V, Citrix Hypervisor/XenServer. Docker Desktop requires nested virtualization, which is not supported by Citrix Hypervisor/XenServer.
>
> Check with your Citrix administrator or VDI infrastructure team to confirm which hypervisor is being used, and whether nested virtualization is enabled.

Title: Docker Cloud Insights, Management, Limitations, and Nested Virtualization Support
Summary
This section covers how to view insights and manage Docker Cloud through the Docker Cloud Dashboard, which provides visibility into builds, runs, and cloud resource usage. It outlines limitations such as the ephemeral nature of containers and data, and usage considerations during the beta phase. The section further discusses Docker's support for running Docker Desktop in virtual desktops with nested virtualization enabled, specifically on VMware ESXi or Azure VMs, and highlights the importance of contacting the hypervisor vendor for troubleshooting issues beyond Docker's control. It also notes that running multiple Docker Desktop instances on the same machine in a VM or VDI environment is not supported.