This error is due to an issue with Service Monitor which affects Sitecore containers based on Windows Server Core LTSC2019. The original entrypoint for the Sitecore CM container in 10.0 used ServiceMonitor.exe
to start and monitor the w3wp
service.
As this issue only affects LTSC2019, one fix is to switch to one of the SAC images available from Sitecore by changing the SITECORE_VERSION
environment variable that's used in the default Compose configuration.
SITECORE_VERSION=10.0.0-1909
Sitecore has also resolved this issue in the latest patch releases for Sitecore 10.0.1 by replacing ServiceMonitor.exe
with a custom script, one that was already being used in Sitecore 10.1. To get this update, ensure your SITECORE_VERSION
is either 10.0-ltsc2019
or 10.0.1-ltsc2019
and pull the latest images:
docker-compose -f .\docker-compose.yml pull
If you are using Sitecore Docker Tools and its development entrypoint, you need to ensure you have the latest patch release of it as well.
docker pull scr.sitecore.com/tools/sitecore-docker-tools-assets:10.0.0-1809
If you are building custom images for your Sitecore containers, after pulling the latest base images and Sitecore Docker Tools images, you'll also need to rebuild your containers.
docker-compose build