New answers tagged

0 votes

Error: The specified module 'SitecoreDockerTools' with version '10.2.7' was not loaded because no valid module file was found in any module directory

To solve this issue, try this solution. Open init.ps1 and use -allowclobber parameter in Install-Module. Refer to this document for installation issues. https://www.bugdebugzone.com/2020/09/install-...
Sumit Bhatia's user avatar
  • 4,945
2 votes
Accepted

XM Cloud with NPM workspaces on local Docker throws "Error: EPERM: operation not permitted, symlink"

Workaround 1 - use Windows Server 2022 for the host machine I managed to eventually find there is an open issue here for this problem. ... the problem exists only when running Windows Server image on ...
Mark Gibbons's user avatar
  • 5,542
0 votes

I'm unable to install headless CMS in sitecore 10.2 Docker Setup?

This error may happen due to the Docker Desktop configuring to Compose V2 mode. Open up Docker Desktop, go to Settings and Uncheck Use Docker Compose V2. Refer to this document for common docker ...
Sumit Bhatia's user avatar
  • 4,945
1 vote

XM Cloud with NPM workspaces on local Docker throws "Error: EPERM: operation not permitted, symlink"

The web is filled with answers and conflicting ideas on how to solve this. I'm taking a guess and suggest, you may be looking at a permission issue. To test this, follow these steps. Assuming Windows ...
Mark Cassidy's user avatar
  • 25.1k
0 votes

SXA Component creation: "Access to the path is denied error"

Adding volume configuration as @Michael West suggested in the comments did solve the permission issue. docker-compose.yml: cm: volumes: - ${LOCAL_DEPLOY_PATH}\website:C:\deploy
Serhii Shushliapin's user avatar
1 vote

SXA Component creation: "Access to the path is denied error"

Dockerfile Permissions: You may try the below if that works.(This is not a general solution this works in my case) You can include the necessary permissions directly in your Dockerfile. Add the ...
Nikhil Kulkarni's user avatar
1 vote
Accepted

My Solr health check during docker compose up is failing in my local xm cloud instance

Found the issue, turns out that it was that docker was not adding solr (or any of the container names) to it's DNS... so when it was trying to iwr against http://solr:8983/*, it could not resolve solr....
Bridgette Ryan's user avatar

Top 50 recent answers are included