Seems like the issue is due to the absence of an escape character in the script. In the
docker-compose.override.yml file located at
docker-examples/custom-images/docker-compose.override.yml, the entry point for the CM node specifies the command as
entrypoint: powershell -Command "& C:\\tools\\entrypoints\\iis\\Development.ps1".
In PowerShell, the ampersand (
&) is used to invoke a script or command. However, the backslash (
\) is an escape character in YAML syntax. To ensure that the backslashes are interpreted correctly and treated as literal characters when executing the PowerShell command, they need to be properly escaped.
To resolve this issue, make sure you include the necessary escape characters when running the script. Here's an example of how the command should be executed:
powershell -Command "& \"C:\\tools\\entrypoints\\iis\\Development.ps1\""
By adding double quotes (
") around the script path and escaping each backslash with another backslash, you ensure that the PowerShell command correctly recognizes the path.
Please give this modified command a try and see if it resolves the problem you encountered while spinning up the CM instance in Docker.