We are experiencing an issue with Docker, Only one user can use docker service in VDI

Question

Hi Support Team,

We are experiencing an issue with Docker Desktop on our Azure Virtual Desktop (AVD) environment and would appreciate your assistance.

Environment:

• Azure Virtual Desktop (Windows 11 Enterprise Multi-Session)
• Docker Desktop (latest version)
• WSL 2 enabled and updated
• Virtual Machine Platform enabled
• Docker Desktop installed using the Administrator account

 

Issue:

• Docker Desktop starts successfully for the first user who logs in and launches Docker.
• When another user logs into the same multi-session host and attempts to use Docker Desktop, it fails to start.
• The second user receives errors such as:
  • "Backend exited before becoming ready"
    • Another user already uses the servcie
      • HTTP 500 Internal Server Error
      • Running docker info also returns a 500 Internal Server Error.
      • We also observed that wsl -l -v does not show the expected Docker WSL distributions when the issue occurs.

 

Troubleshooting performed:

• Verified WSL 2 is installed and up to date.
• Verified the Windows Subsystem for Linux and Virtual Machine Platform features are enabled.
• Confirmed the Docker Desktop service (com.docker.service) is running.
• Reinstalled Docker Desktop.
• Restarted the Docker service and the VM.
• Reviewed Docker backend logs, which indicate that the backend exits before becoming ready.

 

 

Questions:

1. Is Docker Desktop officially supported on Windows 11 Enterprise Multi-Session in Azure Virtual Desktop?
2. Is concurrent Docker Desktop usage by multiple users on the same AVD session host supported?
3. If not, what is the recommended Microsoft-supported architecture for providing Docker access to multiple developers?
4. Are there any recommended configurations or best practices that would allow Docker Desktop to function reliably in a multi-session AVD environment?

 

 

We appreciate your guidance on the supported approach and any recommendations to resolve this issue.

 

Thank you.

Ranveer Singh

Hi Support Team,

1. We purchased developers plan for support, but When I an creating ticket, I am adding necessary detail in support, it always goes to troubleshooting and documentation page. Not able to create direct ticket. So please help me to create a ticket.
2. Actual issue:

We are experiencing an issue with Docker Desktop on our Azure Virtual Desktop (AVD) environment and would appreciate your assistance.

Environment:

• Azure Virtual Desktop (Windows 11 Enterprise Multi-Session)
• Docker Desktop (latest version)
• WSL 2 enabled and updated
• Virtual Machine Platform enabled
• Docker Desktop installed using the Administrator account

 

Issue:

• Docker Desktop starts successfully for the first user who logs in and launches Docker.
• When another user logs into the same multi-session host and attempts to use Docker Desktop, it fails to start.
• The second user receives errors such as:
  • "Backend exited before becoming ready"
    • Another user already uses the servcie
      • HTTP 500 Internal Server Error
      • Running docker info also returns a 500 Internal Server Error.
      • We also observed that wsl -l -v does not show the expected Docker WSL distributions when the issue occurs.

 

Troubleshooting performed:

• Verified WSL 2 is installed and up to date.
• Verified the Windows Subsystem for Linux and Virtual Machine Platform features are enabled.
• Confirmed the Docker Desktop service (com.docker.service) is running.
• Reinstalled Docker Desktop.
• Restarted the Docker service and the VM.
• Reviewed Docker backend logs, which indicate that the backend exits before becoming ready.

 

 

Questions:

1. Is Docker Desktop officially supported on Windows 11 Enterprise Multi-Session in Azure Virtual Desktop?
2. Is concurrent Docker Desktop usage by multiple users on the same AVD session host supported?
3. If not, what is the recommended Microsoft-supported architecture for providing Docker access to multiple developers?
4. Are there any recommended configurations or best practices that would allow Docker Desktop to function reliably in a multi-session AVD environment?

 

 

We appreciate your guidance on the supported approach and any recommendations to resolve this issue.

 

Thank you.

Answer 1

Hello Ranveer Singh,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you're experiencing an issue with Docker, and it's only one user can use docker service in VDI.

Simply because Docker Desktop is not supported for concurrent multi-user use on the same Windows 11 Enterprise multi-session AVD session host. - https://docs.docker.com/desktop/setup/vm-vdi/, https://docs.docker.com/desktop/setup/vm-vdi.md, and https://learn.microsoft.com/en-us/azure/virtual-desktop/windows-multisession-faq gives you more insights.

Since your troubleshooting already proves the main point: WSL 2 is enabled, Virtual Machine Platform is enabled, Docker service is running, Docker was reinstalled, the VM was restarted, and backend logs show Docker exits before becoming ready. These steps do not resolve the issue because the environment design is unsupported for concurrent Docker Desktop sessions.

My advice:

1. Remove Docker Desktop from the pooled multi-session AVD use case and provide each developer with an isolated Docker runtime. The recommended Microsoft-aligned path is Microsoft Dev Box with the Docker Desktop-compatible image, because it gives each developer a dedicated cloud workstation with Docker Desktop, WSL 2, and dependencies preinstalled. - https://marketplace.microsoft.com/en-us/product/virtual-machines/dockerinc1694120899427.devbox_azuremachine?tab=Overview, https://docs.docker.com/enterprise/enterprise-deployment/dev-box/
2. If the organization must continue using AVD, change from a pooled multi-session host model to personal AVD desktops or one dedicated Azure VM per developer, using a VM size that supports the required virtualization features. Docker Desktop may then be installed and used by one developer per VM, not shared concurrently by multiple users on one session host.
3. If the actual requirement is shared container build and deployment rather than the Docker Desktop UI, move the container workflow to Azure-native services such as Azure Container Registry Tasks, CI/CD, AKS, Azure Container Apps, or Azure Container Instances. Azure Container Registry Tasks supports cloud-based container image builds, on-demand builds, and automated builds triggered by source changes, base-image updates, or timers. - https://learn.microsoft.com/en-us/azure/container-registry/container-registry-tasks-overview, https://learn.microsoft.com/en-us/azure/container-registry/
4. For the separate issue where the Developer support plan does not allow creating a direct support ticket, verify that the affected user has the required Azure RBAC permission at the subscription scope. The user must be Owner, Contributor, Support Request Contributor, or have a custom role with Microsoft.Support/*. - https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-manage-azure-support-request Use this command if the user needs only support-ticket permission: az role assignment create --assignee <userObjectIdOrUPN> --role "Support Request Contributor" --scope /subscriptions/<subscriptionId>

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

---

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.