⟵ Resources

Playing around with Sitecore 10.1.1 docker containers and my simple development framework version 3.2

Image of CMSes

Some months ago, I had a chance to play around with Sitecore 10.0.1 docker containers by updating and then deploying the Sitecore solution of my simple development framework successfully. Now I wanted to deploy the Sitecore solution of my simple development framework to Sitecore version 10.1.1 (e.g Sitecore 10.1 Update 1) docker containers as well. As a consequence, my simple Sitecore development framework version 3.2 is out.

By the way, there are some other updates:

  • upgrade to Mapper.Sc.101 latest stable version 5.8.177 (thanks my fellow Sitecore MVP Micheal Edwards)
  • List of Glass.Mapper modules
  • upgrade to Unicorn 4.1.5 + Rainbow 2.1.4(thanks my fellow Sitecore MVPs Mark Cassidy)
  • Unicorn and Unicorn.Core

Step-by-step guide for Sitecore docker container deployment

  1. please ensure to set up your development environment by following https://doc.sitecore.com/developers/100/developer-tools/en/set-up-the-environment.html
  2. create a new folder, let’s say D:my-simple-framework and then download + unzip my simple Sitecore development framework version 3.2
  3. to avoid any conflicts, we should ensure the following ports are not being used by another process: 443, 8079, 8081, 8984, and 14330
    • stop IIS
    • stop windows services if any
    • quit Skype for sure
  4. let’s spin up our own container-based Sitecore 10.1.1 instances:
    • rename D:my-simple-frameworkDocker.env.example to D:my-simple-frameworkDocker.env
    • open Windows PowerShell (run as administrator)
    • change directory to D:my-simple-frameworkDocker
    • execute .Init -InitEnv to initialize environment variables and then input
      • LicenseXmlPath: (Ex: “C:licenselicense.xml”)
      • AdminPassword: (Ex: “b”)
    • Creating hosts files and populating .env file values
    • execute .up to spin up a new Sitecore 10.1.1 instance
    • Downloading various Sitecore components
    • hopefully will see something like this after a loooooooooooog operation
    • Creating various Sitecore components
  5. open a browser, navigate to https://cm.viethoang.local/, we would see the default Sitecore page with a valid SSL certificate
    • Show that the connection is secured
    • don’t forget to verify the Sitecore version 10.1.1
    • Sitecore.NET 10.1.1 license details
  6. let’s deploy the Sitecore solution
    • rename D:my-simple-frameworkcake-config.json.example to cake-config.json then update the following ones
    • WebsiteRoot to deploy folder which is mounted to docker container
    • Showing LOCAL_DEPLOY_PATH values
    • BuildToolVersions to your MS Build version on your own machine (Ex: “VS2019”)
    • WebsiteRoot and BuildToolVersions values
    • rename D:my-simple-frameworkLocalSettings.config.example to Common.LocalSettings.config
    • Value is C:Unicorn
    • Highlight Unicornseria
    • open Windows PowerShell (run as administrator)
    • change directory to D:my-simple-framework
    • execute .build -target Deploy-Docker
    • Running the build script
    • Highlight Publish-Library-Files
    • Note: there is a new Cake build task Publish-Library-Files in order to publish “the version” of library files which are not automatically referenced by the build system but are used by Sitecore
  7. open a browser, navigate to the following ones to access Sitecore sites with HTTPS protocol in the docker environment

Notes:

Happy Sitecore Docker and Coding!

This article originally appeared on Walking on clouds (https://buoctrenmay.com/).

Best Email Writing Tips for 2025

8 Irresistible Tips to Craft Ad Copy That Converts in Paid Online Campaigns

Sitefinity Cache Invalidation

Portfolios

Resources

Contact Us

Website Development Company in Singapore white logo
LowCarbonSG Logo
Terms & Conditions | Privacy Policy | Accessibility Statement

Apply Now!

Upload Resume (with a 2mb maximum file size)
Accepted file types: doc, docx, pdf, xps, Max. file size: 2 MB.
This field is for validation purposes and should be left unchanged.