Skip to content

Latest commit

 

History

History
52 lines (35 loc) · 2.17 KB

vs-azure-tools-docker-troubleshooting-docker-errors.md

File metadata and controls

52 lines (35 loc) · 2.17 KB
title description services documentationcenter author manager editor ms.assetid ms.service ms.devlang ms.topic ms.tgt_pltfrm ms.workload ms.date ms.author
Troubleshooting Docker client errors on Windows by using Visual Studio | Microsoft Docs
Troubleshoot problems you encounter when using Visual Studio to create and deploy web apps to Docker on Windows by using Visual Studio 2017.
azure-container-service
na
devinb
douge
346f70b9-7b52-4688-a8e8-8f53869618d3
multiple
dotnet
article
na
multiple
10/13/2017
devinb

Troubleshoot Visual Studio 2017 development with Docker

When you're working with Visual Studio Tools for Docker, you may encounter issues while building or debugging your application. Below are some common troubleshooting steps.

Volume sharing is not enabled. Enable volume sharing in the Docker CE for Windows settings (Linux containers only)

To resolve this issue:

  1. Right-click Docker for Windows in the notification area, and then select Settings.
  2. Select Shared Drives and share the system drive along with the drive where the project resides.

Note

If files appear shared, you may still need to click the "Reset credentials..." link at the bottom of the dialog in order to re-enable volume sharing.

shared drives

Unable to start debugging

One reason could be related to having stale debugging components in your user profile folder. Execute the following commands to remove these folders so that the latest debugging components are downloaded on the next debug session.

  • del %userprofile%\vsdbg
  • del %userprofile%\onecoremsvsmon

Errors specific to networking when debugging your application

Try executing the script downloadable from Cleanup Container Host Networking, which will refresh the network-related components on your host machine.

Microsoft/DockerTools GitHub repo

For any other issues you encounter, see Microsoft/DockerTools issues.