Standing up a Sitecore 10.2 Instance

Standing up an instance of Sitecore 10.2 on docker is pretty straightforward. The Sitecore team has done an excellent job of covering all the detailed steps required, which if you’ve never stood up an instance of Sitecore running on containers in your local instance is really useful. If that’s you then you should consider reading the developers install guide, otherwise, if you just want a quick guide, continue on.

1. Ensure your local environment meets the requirements in Section 1.2 of the 10.2 Container Installation Guide

2. Download the Sitecore Container Deployment Package and extract. As I am going to be standing up Sitecore XP0 environment copy the contents of ..\SitecoreContainerDeployment.\compose\ltsc2019\xp0 to c:\projects\Sitecore102

3. Make sure you don’t have anything running on the required TCP ports mentioned in section 1.2.3:

Required PortRoleDescription
443TraefikHTTPS Proxy
8079TraefikTraefik Dashboard
8984SolrSolr API and Dashboard
14330SQLSQL Server

You can run the following to see processes using a specific port:

Get-Process -Id (Get-NetTCPConnection -LocalPort 8984).OwningProcess

Alternatively, you can modify your docker-compose file and configure these services to use a different port.

4. Next we need to run PowerShell script compose-init.ps1 in the c:\projects\Sitecore102 directory to prep the deployment. This performs the following actions:

  • Compresses the Sitecore license file
  • Creates the Identity Server token signing certificate
  • Populates the .env file
  • Generates TLS/HTTPS certificates
  • Installs the root certificate into your Trusted Root Certification Authorities
  • Updates Windows host names

The script params are detailed in section 1.3.3, most of these are optional and will use the default values contained in the script if not provided. The only mandatory param is LicenseXmlPath.

.\compose-init.ps1 -Topology “xp0” -LicenseXmlPath “C:\Sitecore\license\2021\license.xml”

5. Once completed all you need to do is run:

docker-compose up -d

6. Once all the containers are up you can access the Sitecore on https://xp0cm.localhost/sitecore using the credentials admin/Password12345


Whenever I first ran the compose-init.ps1 I was getting the following error:

This just means my PowerShell modules are not up-to-date (thanks to Alex Van Wolferen for this tip). To resolve I just needed run the following commands:

Install-Module -Name PackageManagement -Repository PSGallery -Force -AllowClobber

Install-Module -Name PowerShellGet -Repository PSGallery -Force -AllowClobber

Useful Resources

Have Fun!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s