docker · installation

Sitecore XP 10.0 Update 2 – Installation – Docker Way

This blog post is a summary of my own experience for Sitecore Experience Platform 10.0 Update 2 installation on my machine with the following install guide:

Prerequisites

  • Windows 10 version 1809 or higher
  • >= 16 Gb of memory
  • Sitecore 10 license file
  • the latest Docker Desktop

Step-by-step Guide

  1. ensure to set up your docker environment by following https://containers.doc.sitecore.com/docs/environment-setup
  2. try to bypass some common network issues by setting DNS servers in the Docker engine configuration:
    • open Docker Desktop and then select Settings => Docker Engine
    • ensure the value of the "dns" key is set to ["8.8.8.8"] if any
    • click Apply & Restart button
    • sc1001_1
  3. to avoid any conflicts, we should ensure the following ports are not being used by another process: 443, 8079, 8984, and 14330 (Page 6 in Installation Guide for Developer Workstation with Containers)
    •  
    • stop IIS
    • stop windows services if any
    • quit Skype for sure
  4. create a new folder D:\sc1002_install
  5. download and unzip Container Deployment Package
  6. correct the Sitecore version 10.0.2-ltsc2019 in D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0\.evn
    • sc1002_1
  7. create all certificates and initialize the environment file of Windows Server Core version ltsc2019 and XP Single topology (xp0)
    • download init.ps1 and then put it into D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0
    • ensure that this file C:\license\license.xml is available, otherwise will see this error message later License file is not found. or “License not found at ‘C:\license\license.xml’”
    • open Windows PowerShell (run as administrator)
    • change directory to D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0
    • execute .\init.ps1 -LicenseXmlPath C:\license\license.xml
    • sc1002_2
    • Note: able to change other default values as well
    • sc1002_3
  8. pull Sitecore docker images
    • open Windows PowerShell (run as administrator)
    • change directory to D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0
    • execute docker-compose pull
    • sc1002_4
    • sc1002_5
  9. spin up the container-based Sitecore instances
    • open Windows PowerShell (run as administrator)
    • change directory to D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0
    • execute docker-compose up --d
    • sc1002_6
  10. open a browser, navigate to https://cm.sc1002.localhost/, we would see the default Sitecore page and a valid SSL certificate
    • sc1002_7
  11. open a browser, navigate to https://cm.sc1002.localhost/sitecore, we should be able to login with the admin user and b password by default
    • sc1002_8
  12. DON’T FORGET to perform the following thing as well (Page 12 in Installation Guide for Developer Workstation with Containers)
  1.  

Notes

  1. for stopping the Sitecore instances without losing the changes
    • open Windows PowerShell (run as administrator)
    • change directory to D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0
    • execute  docker-compose stop
    • sc1002_9
    • start the Sitecore instances again by executing  docker-compose start
    • sc1002_10
  2. for data cleanup
    • download clean.ps1 and then put it into D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0
    • open Windows PowerShell (run as administrator)
    • change directory to D:\sc1002_install\SitecoreContainerDeployment.10.0.1.004842.266\compose\ltsc2019\xp0
    • execute  docker-compose down
    • execute  .\clean
    • sc1002_11

Happy Sitecore 10.0 Update 2 Installation!

3 thoughts on “Sitecore XP 10.0 Update 2 – Installation – Docker Way

  1. Mình bị lỗi như thế này khi chạy docker-composer up
    Có thể do cái gì hả bạn?
    Creating network “xp-xp1-1010-ltsc2019_default” with the default driver
    Creating xp-xp1-1010-ltsc2019_redis_1 … done Creating xp-xp1-1010-ltsc2019_mssql_1 … done Creating xp-xp1-1010-ltsc2019_solr_1 … done Creating xp-xp1-1010-ltsc2019_solr-init_1 … done Creating xp-xp1-1010-ltsc2019_xdbcollection_1 … done Creating xp-xp1-1010-ltsc2019_xdbautomationrpt_1 … done Creating xp-xp1-1010-ltsc2019_cortexreporting_1 … done Creating xp-xp1-1010-ltsc2019_cortexprocessing_1 … done Creating xp-xp1-1010-ltsc2019_id_1 … done Creating xp-xp1-1010-ltsc2019_xdbrefdata_1 … done Creating xp-xp1-1010-ltsc2019_prc_1 … done Creating xp-xp1-1010-ltsc2019_xdbsearch_1 … done Creating xp-xp1-1010-ltsc2019_xdbautomation_1 … done Creating xp-xp1-1010-ltsc2019_cd_1 … done Creating xp-xp1-1010-ltsc2019_cm_1 … done Creating xp-xp1-1010-ltsc2019_traefik_1 … done
    ERROR: for xdbautomationworker Container “37a8f0c11bb4” is unhealthy.

    ERROR: for xdbsearchworker Container “37a8f0c11bb4” is unhealthy.

    ERROR: for cortexprocessingworker Container “37a8f0c11bb4” is unhealthy.
    ERROR: Encountered errors while bringing up the project.

    Like

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com 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

This site uses Akismet to reduce spam. Learn how your comment data is processed.