Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Note
Docker's licensing requirements might be different for different versions of Docker Desktop. Refer to the Docker documentation to understand the current licensing requirements for using your version of Docker Desktop for development in your situation.
Containers window
The Containers window lets you view containers and images on your machine and see what's going on with them. You can view the filesystem, volumes mounted, environment variables, ports used, and examine log files.
Open the Containers window by using the quick launch (Ctrl+Q) and typing containers. You can use the docking controls to put the window somewhere. Because of the width of the window, it works best when docked at the bottom of the screen.
Select a container, and use the tabs to view the information that's available. To check it out, run your Docker-enabled app, open the Files tab, and expand the app folder to see your deployed app on the container.
For more information, see Use the Containers window.
Docker Compose support
When you want to compose a multi-container solution using Docker Compose, add container orchestrator support to your projects. This lets you run and debug a group of containers (a whole solution or group of projects) at the same time if they're defined in the same docker-compose.yml file.
After you add container orchestrator support to your project, you see a Dockerfile added to the project (if there wasn't one there already) and a docker-compose folder added to the solution in Solution Explorer, as shown here:
If docker-compose.yml already exists, Visual Studio just adds the required lines of configuration code to it.
Repeat the process with the other projects that you want to control using Docker Compose.
If you work with a large number of services, you can save time and computing resources by selecting which subset of services you want to start in your debugging session. See Start a subset of Compose services.
Note
Remote Docker hosts are not supported in Visual Studio tooling.
Service Fabric support
Continuous delivery and continuous integration (CI/CD)
Visual Studio integrates readily with Azure Pipelines for automated and continuous integration and delivery of changes to your service code and configuration. To get started, see Create your first pipeline.
For Service Fabric, see Tutorial: Deploy your ASP.NET Core app to Azure Service Fabric by using Azure DevOps Projects.
Next steps
For further details on the services implementation and use of Visual Studio tools for working with containers, read the following articles:
Container Tools in Visual Studio
Debugging apps in a local container
Deploy an ASP.NET container to a container registry using Visual Studio