Hot answers tagged

15

While currently Sitecore cannot provide guidance on how to develop or host them in a containerized environment other than those examples, but if you are hosting a Sitecore solution within a containerized environment, the Sitecore Support team will assist you with any Sitecore product issues. More details in this KB article: https://kb.sitecore.net/articles/...


12

You need to set the code type to Managed (.NET 4.x) code in the Attach to: section of the Attach to Process dialog in order for debugging to work. Automatic does not load symbols.


10

This error is due to an issue with Service Monitor which affects Sitecore containers based on Windows Server Core LTSC2019. The original entrypoint for the Sitecore CM container in 10.0 used ServiceMonitor.exe to start and monitor the w3wp service. As this issue only affects LTSC2019, one fix is to switch to one of the SAC images available from Sitecore by ...


9

You mentioned in comments that you're getting an error—this is because there is no tag in my docker hub repository. I wouldn't know which version of Sitecore latest should be build against: 8.2 or 8.1 update 3, and on the top of that, which version of SolR. So I choose to go with the tag 8.2. So you would have to pull it with the following command: docker ...


8

Have you previously worked with older versions of Sitecore with Docker? If so, you may still have an environment variable floating around with an invalid license. The getting started project appears to be using the mounted license file strategy. The SITECORE_LICENSE var shouldn't be set, as it is in your screenshot of the id container env vars. Having this ...


8

The solution for this issue was to add SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] before first RUN Invoke-Expression Update: Seems like 20H2 defaults to CMD instead of SHELL.


8

For Azure PaaS infrastructure: Looking at the Azure AppServices packages for a scaled XP solution, you will find that that the following three workers are deployed in their correlated app services and they are configured to run as Azure WebJobs. xConnect Search Indexer - It runs as Azure WebJob in the xConnect Collection Search app service. Marketing ...


7

You cannot mount a volume to an existing directory inside your container on Windows Docker. You need to map up a new directory and then use some means of moving the files to the destination you ultimately want. This is what Watch-Directory takes care of in your entrypoint:. Source: can not mount volume if the directory in container is not empty For the ...


7

After a lot of research and troubleshooting, we were able to resolve this issue. It is caused by a group policy setting which prevents Docker from setting up Windows firewall rules necessary to pass the DNS requests around. I found the root cause buried in the comments of an issue raised for Docker Desktop's open source repo. Resolution Update the Apply ...


7

If the hotfix contains both files and items, I think it should be installed as if it were a module, following the documented approach in the Add Sitecore Modules section of the Sitecore official documentation. This approach requires a module to be distributed as asset image. For a normal Sitecore package, you will need to convert it to a web deploy package (...


6

It looks like it might be related to security policies within our company as I've been able to reproduce the same behaviour on other machines within the company. And it's working OK on non-company machines. The solution that worked for me was to add hostnames to every container. e.g.: mssql: hostname: mssql isolation: ${ISOLATION} ... solr: ...


6

The Horizon asset images currently listed in the /community/modules namespace of the scr have issues that the product team is helping us fix. We will push updated asset images once the fix is in place, the work is happening as we speak and we should have something updated soon. I take the blame for mistakenly pushing those asset images out to the SCR. I will ...


6

I haven't personally used it yet, but I was able to connect successfully Sitecore Rocks with a Sitecore instance running on a cm service container following these steps: 1) If not done yet, add a volume to your cm container service to map the container C:\src folder used by the Watch-Directory script to deploy files in the Sitecore instance. For example: ...


6

This is a known issue with IIS ServiceMonitor, which is used as an entrypoint for Docker images: https://github.com/Microsoft/IIS.ServiceMonitor/issues/32 ServiceMonitor copies environment variables to IIS process on container startup, however it is making them uppercase. This is why you see the error with duplicate PSMODULEPATH entry. Latest version of ...


6

UPDATE March 2018 Docker is still not supported, but you can find some base images here: https://github.com/Sitecore/docker-images This repository was created by combining efforts / assets from repos such as sitecoreops and sitecore-nine-docker and sitecore-docker repos. Docker is currently (as of May 2017) not supported, but it is on the roadmap. On ...


4

UPDATE: Mongo has now released official images: https://hub.docker.com/_/mongo/! As far as I know, no one has created public Windows based images solr yet... That said, it should be pretty easy to do. Here are some examples of creating images for traefik/nginx that I created that can help you get started: traefik.io on "nanoserver": https://github.com/...


4

Quick fix This turned out to be a permissions issue that prevented the ShardMapManager database (and accompanying shard databases) from being installed. To fix it, I needed to give the NETWORK SERVICE account access to the mssql-data folder on my host. More info on troubleshooting Run docker-compose logs mssql to see the logs for the SQL server. In my case, ...


3

The sitecore.aspnet.gettingstarted didn't install SXA to the Sitecore XP0 instance, so I needed to modify the docker files in order to add SPE and SXA to my images. Here is how to do it, if anyone is in the same situation, and need to add a module to their docker-compose file: in .env add the following variables: You'll need mssql to add some databases, ...


3

I faced this issue too during installation. Try the below steps: Run docker-compose stop on Powershell. Run docker-compose down on Powershell. Now run iisreset /stop on Powershell to make sure that the required ports are free. Now run docker-compose up -d on Powershell. Hoping this solves your issue.


3

That might be related to your firewall settings. One of the things you can try is to add custom DNS to Docker engine config file. You can use the Google one - 8.8.8.8 The format is as following: "dns":["8.8.8.8"] It should look like this:


3

A new Docker image must be created. This new image will inherit Sitecore base images. You may have different Dockerfile files for different purposes. One could be for debugging and other could be for release. By using Docker-Compose you can define an environment with a MSSQL container, another Solr container and a Sitecore website container along with the ...


3

Sounds very odd, if you were using Solr Cloud then might have been Zookeeper was down when SOLR started up. Or you might have missed out creating the SOLR aliases. Don't see a mention of SolrCloud or Zookeeper though. Other than checking collections and configs match up. To see what is going on, install Fiddler, change your sitecore app pool to run as ...


3

I've stepped into the same behavior on the same Windows 10, 20H2 update; a friend of mine has no issue on a prev. Windows update as well. The log message has a clue: ...The command 'cmd /S /C Invoke-Expression.. Dockerfile builder somehow defaults to CMD over Powershell; therefore we need to enforce SHELL to use Powershell. Looking at the question from a ...


3

The traefik container depends on the health of CM, CD. What I suggest you first check the health of these containers (use the command "docker ps"). After running this command if you find out the CM or CD container is "unhealthy". To know the real error you need to inspect the container (CM and CD) (use the command "docker container ...


3

I think your scripts are defaulting to use basic CMD as it's shell rather than what you expect; a powershell. Add the following to your relevant docker files. SHELL ["powershell", "-Command", "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"] References: PR that addresses the same problem you are ...


3

Depending on your version of VMware Tools in the Windows OS (mine was 11.0.5), you need to disable VMware's appinfo plugin. On your Docker host, open an Admin PowerShell prompt and run the below command to fix it (you may need to reboot): & 'C:\Program Files\VMware\VMware Tools\VMwareToolboxCmd.exe' config set appinfo disabled true More info This ...


3

Checking the official Sitecore images tags list, it seems that the sitecore-xc0-solr-init image is missing. You should open a ticket with Sitecore Support to let them know that it is missing. In the meantime, you can update the image name of the solr-init service in your docker-compose.yml file to use the existing sitecore-xc1-solr-init image instead (xc1 ...


2

You can find a docker container for mongodb and Solr created by Thomas Stern over at his blog that describes how to use it and get started: https://blog.istern.dk/2016/10/04/solr-docker-container-for-sitecore-8-2/ In addition you can find the project here at github: https://github.com/istern/Sitecore-Containers/tree/master/containers/solr/sitecore8.2 ...


2

So I ended up rebuilding my docker image, this time not using the volumes capability on the docker-compose.yml file. So my file now looks like this: version: "2.1" services: mongodb: image: istern/windows-mongo mssql: image: microsoft/mssql-server-windows-express:latest mem_limit: 2g expose: - "1433" environment: - ...


2

Please note that the Docker image and container identifiers used in the following examples will need to be updated with the values from your own environment. Run a Sitecore container based on an image: docker run -d -m 8GB --name <ContainerName> <ImageNameOrID> Examples: docker run -d -m 8GB -p 80 -p 443 -p8983 --name test dockerhub.io/lfaggiani/...


Only top voted, non community-wiki answers of a minimum length are eligible