Setting Up a Sitecore Developer Environment with Docker Part 1

Now that I have a little more time on my hands (and docker for windows/sitecore is more mature), I decided to try my hand at setting up a full development environment. After spending a little time researching and hearing some stories from co-workers, I knew that my first step was just to just get the environment up and running. I have pretty extensive experience setting up and using docker on linux, but this was also my first foray into docker on windows so I knew I was in for an experience. I started off by using this blog post for a guide. So, I executed git clone https://github.com/Sitecore/docker-images.git locally and ran the provided .\Build.ps1 script, providing my sitecore credentials.

The first issue that I ran into was that the downloading of the sitecore packages seemed to be massively slow using the provided Powershell Script, so I downloaded most of them myself or used some that I already had locally. After a looooooooooong time to download some of the images I ran into my first error!

Getting Base Images to Run

Failed: docker image build --isolation 'hyperv' --memory 4GB --build-arg BASE_IMAGE=mcr.microsoft.com/windows/servercore:ltsc2019 --tag 'mssql-developer:2017-windowsservercore-ltsc2019' 'C:\ScDocker\docker-images\windows\dependencies\mssql-developer-2017' At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:234 char:74 + ... here-Object { $_ } | ForEach-Object { throw "Failed: $buildCommand" } + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Failed: docker ...developer-2017':String) [], RuntimeException + FullyQualifiedErrorId : Failed: docker image build --isolation 'hyperv' --memory 4GB --build-arg BASE_IMAGE=mcr. microsoft.com/windows/servercore:ltsc2019 --tag 'mssql-developer:2017-windowsservercore-ltsc2019' 'C:\ScDocker\doc ker-images\windows\dependencies\mssql-developer-2017'
Was unable to get my docker images to build locally.
Failed: docker image build --isolation 'hyperv' --memory 4GB --build-arg
BASE_IMAGE=mcr.microsoft.com/windows/servercore:ltsc2019 --tag 'mssql-developer:2017-windowsservercore-ltsc2019'
'C:\ScDocker\docker-images\windows\dependencies\mssql-developer-2017'
At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:234 char:74
+ ... here-Object { $_ } | ForEach-Object { throw "Failed: $buildCommand" }
+                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Failed: docker ...developer-2017':String) [], RuntimeException
    + FullyQualifiedErrorId : Failed: docker image build --isolation 'hyperv' --memory 4GB --build-arg BASE_IMAGE=mcr.
   microsoft.com/windows/servercore:ltsc2019 --tag 'mssql-developer:2017-windowsservercore-ltsc2019' 'C:\ScDocker\doc
  ker-images\windows\dependencies\mssql-developer-2017'

This one confused me for a bit and I asked for a bit of help from the sitecore slack docker channel and received a reply from Michael West to just try to get a docker nano image up and running. (I honestly should have tried this and Hello World first).

Getting Docker to Run

So, my next step was to run docker run docker run mcr.microsoft.com/windows/nanoserver:1903

I ended up with this result:

PS C:\ > docker run mcr.microsoft.com/windows/nanoserver:1903 Unable to find image 'mcr.microsoft.com/windows/nanoserver:1903' locally 1903: Pulling from windows/nanoserver 44ae645d6437: Pull complete Digest: sha256:f652326ab5a165acf88727ec4365b63e0705f565633fba7042772dc701ed5f97 Status: Downloaded newer image for mcr.microsoft.com/windows/nanoserver:1903 C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: hcsshim::CreateComputeSystem e551a02ed4177871fed1d9a6a619a9338b189267edec1fcca4ea8bc340231345: The virtual machine could not be started because a required feature is not installed. (extra info: {"SystemType":"Container","Name":"e551a02ed4177871fed1d9a6a619a9338b189267edec1fcca4ea8bc340231345","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\Docker\\windowsfilter\\e551a02ed4177871fed1d9a6a619a9338b189267edec1fcca4ea8bc340231345","Layers":[{"ID":"e3faff3f-5920-54a7-ad43-125d32e2a6a7","Path":"C:\\ProgramData\\Docker\\windowsfilter\\1a2574cb8e3b09e348e19d976e006c683699377bba6910ce3bc7b9635e73c317"}],"HostName":"e551a02ed417","HvPartition":true,"EndpointList":["D592B7B6-412C-434F-BC5E-11AF6B8AE692"],"HvRuntime":{"ImagePath":"C:\\ProgramData\\Docker\\windowsfilter\\1a2574cb8e3b09e348e19d976e006c683699377bba6910ce3bc7b9635e73c317\\UtilityVM"},"AllowUnqualifiedDNSQuery":true}).
PS C:\ > docker run mcr.microsoft.com/windows/nanoserver:1903                                            
Unable to find image 'mcr.microsoft.com/windows/nanoserver:1903' locally
1903: Pulling from windows/nanoserver
44ae645d6437: Pull complete                                                                                             Digest: sha256:f652326ab5a165acf88727ec4365b63e0705f565633fba7042772dc701ed5f97
Status: Downloaded newer image for mcr.microsoft.com/windows/nanoserver:1903
C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: hcsshim::CreateComputeSystem e551a02ed4177871fed1d9a6a619a9338b189267edec1fcca4ea8bc340231345: The virtual machine could not be started because a required feature is not installed.
(extra info: {"SystemType":"Container","Name":"e551a02ed4177871fed1d9a6a619a9338b189267edec1fcca4ea8bc340231345","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\Docker\\windowsfilter\\e551a02ed4177871fed1d9a6a619a9338b189267edec1fcca4ea8bc340231345","Layers":[{"ID":"e3faff3f-5920-54a7-ad43-125d32e2a6a7","Path":"C:\\ProgramData\\Docker\\windowsfilter\\1a2574cb8e3b09e348e19d976e006c683699377bba6910ce3bc7b9635e73c317"}],"HostName":"e551a02ed417","HvPartition":true,"EndpointList":["D592B7B6-412C-434F-BC5E-11AF6B8AE692"],"HvRuntime":{"ImagePath":"C:\\ProgramData\\Docker\\windowsfilter\\1a2574cb8e3b09e348e19d976e006c683699377bba6910ce3bc7b9635e73c317\\UtilityVM"},"AllowUnqualifiedDNSQuery":true}).

This one took me a little while to figure out. I ended up fixing it using the following steps (ultimately taken from looking at these sources 1 & 2):

  • Un-installed Hyper-V
  • Un-installed Docker Desktop
  • Restarted Machine
  • Installed Hyper-V and restarted machine
  • Installed Docker Desktop and restarted
  • Ran the command bcdedit /sethypervisorlaunchtype auto in the Powershell command line as administrator
  • Restarted the machine

After that sequence, hello world and the the nano server could run fine. Naturally I went back and figured the Build would finish fine. However, I got the below error pretty quickly.

23:09:09:259: Build specifications loaded... Error response from daemon: Get https://mcr.microsoft.com/v2/windows/servercore/manifests/ltsc2019: EOF Failed. At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:115 char:78 + ... CODE -ne 0 | Where-Object { $_ } | ForEach-Object { throw "Failed." } +                                                         ~~~~~~~~~~~~~~~     + CategoryInfo          : OperationStopped: (Failed.:String) [], RuntimeException     + FullyQualifiedErrorId : Failed.
23:09:09:259: Build specifications loaded...
Error response from daemon: Get https://mcr.microsoft.com/v2/windows/servercore/manifests/ltsc2019: EOF
Failed.
At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:115 char:78
+ ... CODE -ne 0 | Where-Object { $_ } | ForEach-Object { throw "Failed." }
+                                                         ~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Failed.:String) [], RuntimeException
    + FullyQualifiedErrorId : Failed.

I got past this error by manually pulling the ltsc image down and retrying the build script. Then I got another really fun error.

curl: (6) Could not resolve host: go.microsoft.com curl: (6) Could not resolve host: go.microsoft.com Start-Process : This command cannot be run due to the error: The system cannot find the file specified. At line:1 char:319 + ... id=840944'; Start-Process -FilePath 'C:\\install\\SQL.exe' -ArgumentL ... +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : InvalidOperation: (:) [Start-Process], InvalidOp    erationException     + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.C    ommands.StartProcessCommand  Failed: docker image build --isolation 'hyperv' --memory 4GB --build-arg BASE_IMAGE=mcr.microsoft.com/windows/servercore:ltsc2019 --tag 'mssql-developer:2017-windowsservercore-ltsc2019' 'C:\ScDocker\docker-images\windows\dependencies\mssql-developer-2017' At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:234 char:74 + ... here-Object { $_ } | ForEach-Object { throw "Failed: $buildCommand" }
curl: (6) Could not resolve host: go.microsoft.com
curl: (6) Could not resolve host: go.microsoft.com
Start-Process : This command cannot be run due to the error: The system cannot
find the file specified.
At line:1 char:319
+ ... id=840944'; Start-Process -FilePath 'C:\\install\\SQL.exe' -ArgumentL ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Start-Process], InvalidOp
   erationException
    + FullyQualifiedErrorId : InvalidOperationException,Microsoft.PowerShell.C
   ommands.StartProcessCommand

Failed: docker image build --isolation 'hyperv' --memory 4GB --build-arg
BASE_IMAGE=mcr.microsoft.com/windows/servercore:ltsc2019 --tag 'mssql-developer:2017-windowsservercore-ltsc2019'
'C:\ScDocker\docker-images\windows\dependencies\mssql-developer-2017'
At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:234 char:74
+ ... here-Object { $_ } | ForEach-Object { throw "Failed: $buildCommand" }

Luckily a generous soul named Sitecore Gabe had this post, and I set my docker DNS to Google’s 8.8.8.8 and chugged along. I eventually ran into some errors where the hash was invalid for a few of the packages, so I just deleted those and let the script re-download them. I finally got a clean build! I ran docker-compose -f ./docker-compose.xp.yml up from the 9.3.x test folder and had a running version of xp in a couple of minutes. This wasn’t enough for me though, because I want to develop against JSS and have some of the sexier features available to me.

Running XP with SXA and JSS

The next logical step I took was to just go ahead and run docker-compose -f ./docker-compose.xp.sxa.ps.jss.yml up in the same directory and wait for my awesome environment to spin up. Instead…

ERROR: pull access denied for sitecore-xp-sxa-ps-jss-sqldev, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
ERROR: pull access denied for sitecore-xp-sxa-ps-jss-sqldev, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

I do a little digging into the Build.ps1 script and see that I need to include some parameters to get the goodies.

C:\ScDocker\docker-images> .\Build.ps1 -IncludeSpe -IncludeSxa -IncludeJss
Successful Build!

This does not produce all the images though. When running docker-compose -f ./docker-compose.xp.sxa.ps.jss.yml up I still get some errors. More digging in the build.json for some of the images tells me that I need to build experimental as well to get services such as the Publishing Service included. Running with this parameter was the cause of a pretty large headache as I continued on.

C:\ScDocker\docker-images> .\Build.ps1 -IncludeSpe -IncludeSxa -IncludeJss  -IncludeExperimental

COPY failed: CreateFile \\?\Volume{888d15bf-6318-44dc-b4b2-47340eaebfec}\packages\Sitecore Publishing Module 9.3.0.0.scwdp.zip: The system cannot find the file specified.
Failed: docker image build --isolation 'hyperv' --build-arg
BASE_IMAGE=sitecore-xp-standalone:9.3.0-windowsservercore-ltsc2019 --build-arg
ASSETS_IMAGE=sitecore-assets:9.3.0-nanoserver-1809 --build-arg ASSETS_USE_WDP='C:\packages\Sitecore Publishing Module
9.3.0.0.scwdp.zip' --tag 'sitecore-xp-ps-standalone:9.3.0-windowsservercore-ltsc2019'
'C:\ScDocker\docker-images\windows\9.x.x\sitecore-ps'
At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:234 char:74
+ ... here-Object { $_ } | ForEach-Object { throw "Failed: $buildCommand" }
+                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Failed: docker ....x\sitecore-ps':String) [], RuntimeException
    + FullyQualifiedErrorId : Failed: docker image build --isolation 'hyperv' --build-arg BASE_IMAGE=sitecore-xp-stand
   alone:9.3.0-windowsservercore-ltsc2019 --build-arg ASSETS_IMAGE=sitecore-assets:9.3.0-nanoserver-1809 --build-arg
  ASSETS_USE_WDP='C:\packages\Sitecore Publishing Module 9.3.0.0.scwdp.zip' --tag 'sitecore-xp-ps-standalone:9.3.0-w
 indowsservercore-ltsc2019' 'C:\ScDocker\docker-images\windows\9.x.x\sitecore-ps'

I took a look at a few different sources, but the readme showed me that I needed to run the Download-PS-Prerequisites.ps1 script included in the repo. Eventually I had to Install DacFX and a later version of SQL server since I had a weird condition from having installed a version of SQL Server Manager first.

Web Deploy Package Creation Issue
Convert to WDP C:\ScDocker\docker-images\packages\Sitecore Publishing Module 9.3.0.0 rev. r00546.2197.zip
Microsoft.Web.Deployment.DeploymentDetailedFatalException: The SQL provider cannot run with dacpac option because of a missing dependency. Please make sure that DacFx is installed.  Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DACFX_NEEDED_FOR_SQL_PROVIDER.
   at Microsoft.Web.Deployment.DacHelper.ThrowIfDACCannotBeLoaded()
   at Microsoft.Web.Deployment.SqlDacPacProvider.GetAttributes(DeploymentAddAttributeContext addContext)
   at Microsoft.Web.Deployment.DeploymentObject.EnsureValidAttributes()
   at Microsoft.Web.Deployment.ManifestProvider.GetAttributes(DeploymentAddAttributeContext addContext)
   at Microsoft.Web.Deployment.DeploymentObject.EnsureValidAttributes()
   at Microsoft.Web.Deployment.DeploymentObject.get_IsValid()
   at Microsoft.Web.Deployment.DeploymentManager.CreateObjectPrivate(DeploymentProviderContext providerContext, DeploymentBaseOptions baseOptions, DeploymentObject sourceObject, String serverVersion)
   at Microsoft.Web.Deployment.DeploymentManager.CreateObject(DeploymentProviderOptions providerOptions, DeploymentBaseOptions baseOptions)
   at Sitecore.Cloud.Packaging.WebDeployPackages.WebDeployPackageBuilder.MSDeploySyncFromManifest(String manifestXmlPath, String tempPackage)
   at Sitecore.Cloud.Packaging.WebDeployPackages.WebDeployPackageBuilder.Build(SitecoreModuleFolderTree smTree, DirPath outputDir, String sourceName, String[] disableDacPacOptions, Boolean force)
   at Sitecore.Cloud.Cmdlets.Packaging.ConvertToSCModuleWebDeployPackage.ProcessRecord()
ConvertTo-SCModuleWebDeployPackage : Microsoft.Web.Deployment.DeploymentDetailedFatalException: The SQL provider
cannot run with dacpac option because of a missing dependency. Please make sure that DacFx is installed.  Learn more
at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DACFX_NEEDED_FOR_SQL_PROVIDER.
   at Microsoft.Web.Deployment.DacHelper.ThrowIfDACCannotBeLoaded()
   at Microsoft.Web.Deployment.SqlDacPacProvider.GetAttributes(DeploymentAddAttributeContext addContext)
   at Microsoft.Web.Deployment.DeploymentObject.EnsureValidAttributes()
   at Microsoft.Web.Deployment.ManifestProvider.GetAttributes(DeploymentAddAttributeContext addContext)
   at Microsoft.Web.Deployment.DeploymentObject.EnsureValidAttributes()
   at Microsoft.Web.Deployment.DeploymentObject.get_IsValid()
   at Microsoft.Web.Deployment.DeploymentManager.CreateObjectPrivate(DeploymentProviderContext providerContext,
DeploymentBaseOptions baseOptions, DeploymentObject sourceObject, String serverVersion)
   at Microsoft.Web.Deployment.DeploymentManager.CreateObject(DeploymentProviderOptions providerOptions,
DeploymentBaseOptions baseOptions)
   at Sitecore.Cloud.Packaging.WebDeployPackages.WebDeployPackageBuilder.MSDeploySyncFromManifest(String
manifestXmlPath, String tempPackage)
   at Sitecore.Cloud.Packaging.WebDeployPackages.WebDeployPackageBuilder.Build(SitecoreModuleFolderTree smTree,
DirPath outputDir, String sourceName, String[] disableDacPacOptions, Boolean force)
   at Sitecore.Cloud.Cmdlets.Packaging.ConvertToSCModuleWebDeployPackage.ProcessRecord()
At C:\ScDocker\docker-images\Download-PS-Prerequisites.ps1:99 char:5
+     ConvertTo-SCModuleWebDeployPackage -Path $_ -Destination $Destina ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (Microsoft.Web.D...ProcessRecord():String) [ConvertTo-SCModuleWebDeployPac
   kage], Exception
    + FullyQualifiedErrorId : 0,Sitecore.Cloud.Cmdlets.Packaging.ConvertToSCModuleWebDeployPackage

Next, I used this Sitecore Knowledge Base Article to fix my registry entries (after restarting the Powershell terminal) and I was on to the most frustrating error of this process.

Copy-Item : Cannot find path 'C:\temp\Content\Website' because it does not exist. At line:1 char:154 + ... 'C:\\temp'; Copy-Item -Path 'C:\\temp\\Content\\Website\\*' -Destinat ... +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : ObjectNotFound: (C:\temp\Content\Website:String)     [Copy-Item], ItemNotFoundException     + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyI    temCommand  The command 'powershell -Command $ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; Expand-Archive -Path 'C:\\temp\\packages\\*.zip' -DestinationPath 'C:\\temp';     Copy-Item -Path 'C:\\temp\\Content\\Website\\*' -Destination 'C:\\inetpub\\wwwroot' -Recurse -Force;' returned a non-zero code: 1 Failed: docker image build --isolation 'hyperv' --build-arg BASE_IMAGE=sitecore-xp-cd:9.3.0-windowsservercore-ltsc2019 --build-arg ASSETS_IMAGE=sitecore-assets:9.3.0-nanoserver-1809 --build-arg ASSETS_USE_WDP='C:\packages\Sitecore Publishing Module 9.3.0.0.scwdp.zip' --tag 'sitecore-xp-ps-cd:9.3.0-windowsservercore-ltsc2019' 'C:\ScDocker\docker-images\windows\9.x.x\sitecore-ps' At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:234 char:74 + ... here-Object { $_ } | ForEach-Object { throw "Failed: $buildCommand" } +                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : OperationStopped: (Failed: docker ....x\sitecore-ps':String) [], RuntimeException     + FullyQualifiedErrorId : Failed: docker image build --isolation 'hyperv' --build-arg BASE_IMAGE=sitecore-xp-cd:9    .3.0-windowsservercore-ltsc2019 --build-arg ASSETS_IMAGE=sitecore-assets:9.3.0-nanoserver-1809 --build-arg ASSETS   _USE_WDP='C:\packages\Sitecore Publishing Module 9.3.0.0.scwdp.zip' --tag 'sitecore-xp-ps-cd:9.3.0-windowsserverc  ore-ltsc2019' 'C:\ScDocker\docker-images\windows\9.x.x\sitecore-ps'
Copy-Item : Cannot find path 'C:\temp\Content\Website' because it does not
exist.
At line:1 char:154
+ ... 'C:\\temp'; Copy-Item -Path 'C:\\temp\\Content\\Website\\*' -Destinat ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\temp\Content\Website:String)
    [Copy-Item], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyI
   temCommand

The command 'powershell -Command $ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue'; Expand-Archive -Path 'C:\\temp\\packages\\*.zip' -DestinationPath 'C:\\temp';     Copy-Item -Path 'C:\\temp\\Content\\Website\\*' -Destination 'C:\\inetpub\\wwwroot' -Recurse -Force;' returned a non-zero code: 1
Failed: docker image build --isolation 'hyperv' --build-arg
BASE_IMAGE=sitecore-xp-cd:9.3.0-windowsservercore-ltsc2019 --build-arg
ASSETS_IMAGE=sitecore-assets:9.3.0-nanoserver-1809 --build-arg ASSETS_USE_WDP='C:\packages\Sitecore Publishing Module
9.3.0.0.scwdp.zip' --tag 'sitecore-xp-ps-cd:9.3.0-windowsservercore-ltsc2019'
'C:\ScDocker\docker-images\windows\9.x.x\sitecore-ps'
At C:\ScDocker\docker-images\modules\SitecoreImageBuilder\1.0.0\Public\Invoke-Build.ps1:234 char:74
+ ... here-Object { $_ } | ForEach-Object { throw "Failed: $buildCommand" }
+                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Failed: docker ....x\sitecore-ps':String) [], RuntimeException
    + FullyQualifiedErrorId : Failed: docker image build --isolation 'hyperv' --build-arg BASE_IMAGE=sitecore-xp-cd:9
   .3.0-windowsservercore-ltsc2019 --build-arg ASSETS_IMAGE=sitecore-assets:9.3.0-nanoserver-1809 --build-arg ASSETS
  _USE_WDP='C:\packages\Sitecore Publishing Module 9.3.0.0.scwdp.zip' --tag 'sitecore-xp-ps-cd:9.3.0-windowsserverc
 ore-ltsc2019' 'C:\ScDocker\docker-images\windows\9.x.x\sitecore-ps'

I really banged my head on this one for a couple days, trying all kinds of things. The eventual answer was that one of my original downloaded packages (mainly the PS one in my case) was incorrect because I didn’t have the Azure Toolkit converting it to scwdp. So, the asset image that I was using was incorrect. I ran docker rmi sitecore-assets:9.3.0-nanoserver-1809 and got that successful build I had waited so long to see.

Running docker-compose -f .\docker-compose.xp.sxa.ps.jss.yml up got me up and running finally!

Base sitecore home screen
Finally got to see this site in docker.
Sitecore Launchpad
Double checked the sitecore launchpad

Leave a Reply