Sitecore / Sitecore/docker-examples
In the getting-started docker-compose.yml, should xconnect depend on solr or solr-init?
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 82
- Forks
- 110
- Avg merge
- 7d 59m
- Merged PRs (30d)
- 1
Description
I tried running a docker compose up from getting-started in this repo (after running ./init.ps1), and it started solr, mssql, and id, but nothing else, and exited with a message about solr-init not having a health check. A few more tries resulted in the same error message.
When I changed xconnect to depend on solr instead of solr-init (which probably worked since solr-init had already run once), then a lot more stuff started to happen when I ran docker compose up.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with getting-started/docker-compose.yml and reproduce the reported behavior by running ./init.ps1 followed by docker compose up from getting-started. Compare the xconnect dependency with the available Solr services and their health checks; done means the documented startup completes without the solr-init health-check error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, powershell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100