A Windows service is a background process managed by Windows. Core services handle operating-system work such as instrumentation and DNS lookups, commonly through svchost.exe. section 13.2
Windows Server Containers expose a containerization challenge: IIS runs as a Windows service, while Docker expects one monitored entry-point process. The application worker process, w3wp.exe, is not enough for Docker to track service health. section 13.2
Bridge the service model to Docker with:
- Service Monitor, which starts and watches a chosen Windows service, then ends the container if that service fails. section 13.2
- Log Monitor, which reads logs from sources such as log files and the Windows Event Log. section 13.2
# build using the default 2025 OS version: docker build -t diamol/ch13-aspnet:2e .\aspnet # if you get a manifest error, set the version to be 2019 or 2022: # docker build --build-arg WINDOWS_VERSION='ltsc2022' ` # -t diamol/ch13-aspnet:2e .\aspnet # run the container in the background: docker run --name aspnet -d -p 8084:80 diamol/ch13-aspnet:2e # look at the container processes: docker top aspnet
Run an ASP.NET Windows container and inspect its processes with docker top to see service-hosted application behavior. section 13.2
