ERROR: traefik, xdbautomationworker, Container is unhealthy

Question

Trying to create sitecore 10 image using Docker on Windows 10 Enterprise locally but getting unhealthy containers. Please help me out as I have tried various steps that was updated in the forums.

Getting below errors:

Creating network "sitecore-xp0_default" with the default driver
Creating sitecore-xp0_solr_1  ... done
Creating sitecore-xp0_mssql_1 ... done
Creating sitecore-xp0_id_1        ... done
Creating sitecore-xp0_solr-init_1 ... done
Creating sitecore-xp0_xconnect_1  ... done
Creating sitecore-xp0_cm_1        ... done

ERROR: for cortexprocessingworker  Container "992574e988e3" is unhealthy.

ERROR: for xdbautomationworker  Container "992574e988e3" is unhealthy.

ERROR: for xdbsearchworker  Container "992574e988e3" is unhealthy.

ERROR: for traefik  Container "933b548fc2f9" is unhealthy.
ERROR: Encountered errors while bringing up the project.

Checked the following things:

docker-compose stop on Powershell.

docker-compose down on Powershell.

iisreset /stop on Powershell to make sure that the required ports are free.

docker-compose up -d on Powershell.

Stopped, removed the container and executed the command docker-compose.exe up --detach multiple times but no luck.

Answer 1

The traefik container will always be unhealthy if one of the dependent on new are unhealthy, so I wouldn't focus on that.

Should each of the xconnect workers not be on a separate container? Reason I ask is the error shown for each references the same container id 992574e988e3.

Are you able to see any logs for container 992574e988e3?

Answer 2

Based on the logs now provided in the comments above, my suggestion would be to check the collection SQL connection string, to the shardsmanager database.

You can inspect the SQL container in docker for Windows and find the IP address of the SQL server. Connect to that using ssms and try connecting with the creds you have in current string.

Edit: looking again at the exception, it looks like it can't find the SQL server. Yet the CM server appears to not have a problem finding the same server. So compare the web/master/core connection string to the collection one. I'm guessing the SQL server portion will be different?

Answer 3

Check the.env file and make sure SITECORE_LICENSE has a value.

You may need to run the init.ps1 file.