I am at a major lost in how to use docker to create a basic core with pre done schema . None of the documentation explain basic concepts like if I need to create docker compose to cp data from my repo to a docker image or how I can boot into an image in ssh which is basically useless to debug at the moment.
But lets keep this simple
Even using a basic docker solr six image ends with job failed
if I try to precreate a core it fails.
I have no idea how to debug an docker image
What steps can I take to start making sense of this.
Starting Solr 6.6.4
2018-08-02 20:04:18.402 INFO (main) [ ] o.e.j.s.Server Started @1696ms
Job was canceled
Why is it cancelled?
Readers would need to see your config to answer this question. Please add that to your post, using the code-formatting tool available (please format logs with this as well, it makes them more readable).
That isn’t helpful. Literally all there is, is
- image: 'solr:6.6'
Adding my configuration doesn’t give any more clarification. Also I have zero understanding of how to actually format these logs in this lousy wsywig.
Don’t take my reply to heart: you may find it hard to get the help you need from a low-traffic forum like this. You’re already frustrated, which is not an ideal state of mind to learn the things you need, and taking a sharp tone to the one person who does reply to you is rather counterproductive.
On top, you are aware you need to learn how to use Markdown formatting, but blame the software for being “lousy” rather than just learning how to use it. Discourse is in fact excellent open-source software, and is very popular. Markdown is used in GitHub, Stack Overflow, BitBucket, Jira, Reddit, etc - it is unavoidable these days
My advice, which I give frequently here, is that CI is hard. Be patient with yourself, and with others.
I haven’t used Solr, but if you want to get going on quickly, you may find installing it in your primary build container easier than running it in a secondary container. Just use
apt-get install in the way you would with Debian Linux, drop the secondary container, and start it up in its own run step. I would also recommend adding a wait step, so that your build does not continue until the server is ready to accept requests.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.