New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker installation fails to build due to apparent Solr schema version conflict #2255
Comments
It's because the image on docker hub is out of date. If you rebuild the solr docker image, it will work correctly (you may have to do some finagling as symlinks don't work with docker build) |
yes the ckan/solr image (https://registry.hub.docker.com/u/ckan/solr/) needs to be rebuild to use the new schema.xml updated here: #1883 I created a new ckan/solr image which you can use until the official image is updated: |
Another approach using the current ckan/solr image is to run it and mount the new schema.xml into it: The latest schema is at https://github.com/ckan/ckan/blob/master/ckan/config/solr/schema.xml With the latest schema.xml in you current directory run ckan/solr as:
|
Another alternative is to create your own dockerfile that overrides schema.xml (check my comment at docker hub for an example). |
Thank you @milafrerichs for publishing a working container (and others for alternative workarounds). I'm looking forward to the official CKAN container being updated. |
You're welcome. |
Think Solr is still broken on the official one as just tried it. The schema fix posted on April 2 seemed to get further (i.e it managed to start up ckan) but then there are a lot of issues trying to use datasets. There are alot of internal servers errors pointing back to the SOLR issues. |
This project is so hard to use and even harder to maintain I've given up and am searching for other solutions. I recommend you do the same.
|
Thanks for the heads up. Did you mean the docker/ckan or ckan itsself Managed to get it working in the end (but needed to use milafrerichs image https://registry.hub.docker.com/u/milafrerichs/ckan_solr/ ). Started up no errors, and then I needed to add an ADMIN like below with docker (NB:It will prompt to confirm user/password) - This is how you can then log in and add data sets to set things up. docker run -i -t --link db:db --link solr:solr \ ckan/ckan \ /sbin/my_init -- \ /bin/bash -c \ '$CKAN_HOME/bin/paster --plugin=ckan sysadmin -c $CKAN_CONFIG/ckan.ini add administrator' |
If you just need a working CKAN in docker containers, have you tried www.datacats.com? Did the trick for me and took away the solr headaches. |
The open source ckan docker tools from datacats are now at https://github.com/datacats/datacats |
There are several people complaining publicly elsewhere too:
I suggest we change our instructions to suggest people use Datacats: https://github.com/datacats/datacats because it's got some use from several people in the community and when issues arise they are looked at and solved quickly e.g. datacats/datacats#334 There was also the effort from @clementmouchet https://github.com/ckan/ckan-docker that looked good when it appeared last year, but that's had not any input for 6 months now. |
+1 for datacats - always helpful and quick to fix. |
Hi there, Happy to discuss options with you. |
I was bitten by this issue as well. Solved by using datacats instead 👍 |
@clementmouchet When you say "archive it", do you mean the whole CKAN project or just this Docker install? If the latter, will the datacats one then become the "de facto" install? In that case, can you please update the CKAN install page (http://docs.ckan.org/en/latest/maintaining/installing/install-using-docker.html) to redirect folk there instead of here -- right now we are all encountering the same issue (which gives a poor first impression of a major project). |
I've now done a PR to stop people going down this bad route: #2821 |
@davidread Thanks! Unfortunately, the datacats approach does not work either. |
So, does anybody has credentials to update (or remove) solr on Docker Hub? |
@nickstenning has the credentials for https://hub.docker.com/r/ckan/ I believe |
For those how want use the docker image for solr that works with the ckan/ckan docker image:
And for any contribution: |
@miguelbgouveia Isn't it |
You right @shabeermothi the command is: Tks. |
Even after using solr image from Am following the below series of steps : This is the error i get every time :
|
I seams that is a problem only with ckan\ckan container and not with miguelbgouveia/solr-docker or milafrerichs/ckan_solr. |
What's the best way to run CKAN in docker ? |
@shabeermothi since active development on datacats has ceased, Link Digital's AWS-based install looks tasty. |
I just went thru the docker build process and I am getting the same error message as others before: the last line complains that solr needs schema from [2.7]. what I don't understand is that the docker hub says all three repos (ckan/ckan, ckan/postgresql, & ckan/solr) were updated today. Is anybody (the contribitor) looking at the repos and making sure they are functioning repos ? |
This should be updated to dev-2.7 https://github.com/ckan/ckan/blob/master/contrib/docker/solr/Dockerfile#L16 |
@wardi There is no dev-v2.7 yet. Do you mean master? |
Looks like #3346 should address this |
This bug is also present in the packaged version of ckan and starting in ckan 2.5 and also in 2.6. The work-a-round that I found is to install ckan version 2.4 (packaged) and than install 2.5 or 2.6. |
#3867 is causing Docker build to fail. |
Is this all resolved by https://github.com/ckan/ckan/tree/master/contrib/docker now ? |
Good spot. The 'install-from-docker' docs in the title has since been removed in favour of: http://docs.ckan.org/en/2.8/maintaining/installing/install-from-docker-compose.html so I'm closing. Summary:
|
I followed the Docker installation instructions, and while the Solr and Postgresql containers are running, CKAN fails to build.
Supporting services are running, but then (running it interactively to see logs):
Clearly there's a version conflict or a version string set incorrectly, but I'm not familiar enough with CKAN to understand how I might go about resolving this.
The text was updated successfully, but these errors were encountered: