| title | Learn how to set the container entry point for Docker containers in Visual Studio |
|---|---|
| author | ghogen |
| description | Understand and configure the custom container entry point set by Visual Studio based on the project type and the container operating system. |
| ms.author | ghogen |
| ms.date | 9/10/2025 |
| ms.subservice | container-tools |
| ms.topic | how-to |
A container entry point is a process that is configured to run when a container is started.
:::moniker range="visualstudio"
- Docker Desktop or Podman Desktop.
- Visual Studio, or for Podman support, Visual Studio 2026, with the ASP.NET and web development, Azure development workload, and/or .NET desktop development workload installed.
:::moniker-end ::: moniker range="vs-2022"
- Docker Desktop.
- Visual Studio with the ASP.NET and web development, Azure development workload, and/or .NET desktop development workload installed.
:::moniker-end
Visual Studio uses a custom container entry point depending on the project type and the container operating system, here are the different combinations:
:::moniker range="vs-2022"
| Container type | Entry point |
|---|---|
| Linux containers | For .NET 6 and later, the entry point is dotnet --roll-forward Major /VSTools/DistrolessHelper/DistrolessHelper.dll --wait. For .NET 5 and earlier, the entry point is tail -f /dev/null. These processes use an infinite wait to keep the container running when the app is not running. When the app is launched, with or without debugging, it's the debugger that is responsible to run the app (that is, dotnet webapp.dll) and keep the container running. |
| Windows containers | The entry point is something like C:\remote_debugger\x64\msvsmon.exe /noauth /anyuser /silent /nostatus which runs the debugger, so it's listening for connections. For .NET Framework web apps, the entry point is slightly different where ServiceMonitor is added to the command. |
| :::moniker-end |
:::moniker range="visualstudio"
| Container type | Entry point |
|---|---|
| Linux containers | For .NET 6 and later, the entry point is dotnet --roll-forward Major /VSTools/DistrolessHelper/DistrolessHelper.dll --wait. For .NET 5 and earlier, the entry point is tail -f /dev/null. These processes use an infinite wait to keep the container running when the app is not running. When the app is launched, with or without debugging, it's the debugger that is responsible to run the app (that is, dotnet webapp.dll). DistrolessHelper monitors the app process, and exits with the app's exit code when the app process ends. |
| Windows containers | The entry point is something like C:\remote_debugger\x64\msvsmon.exe /noauth /anyuser /silent /nostatus which runs the debugger, so it's listening for connections. |
| :::moniker-end |
The container entry point can only be modified in Docker Compose projects, not in single-container projects. See Docker Compose properties - Customize the app startup process.