Are there any other prerequisites? We followed the instructions in the readme, but are getting endless errors it seems. 
We got rid of the $$ and changed it back to $, and updated the volume to include a â:rwâ at the end since thatâs what the error was giving us. Now we are getting another error about not being able to connect to the Docker daemon at http+docker://localunixsocket
Apologies for being so clueless⊠Weâve never worked with docker before
I am also running Docker version 1.13.1, build 092cba3 (for mac).
I did the following (slightly simplified for testing; I didnât fork):
git clone GitHub - OpenConceptLab/oclapi: Deprecated. Please see https://github.com/OpenConceptLab/oclapi2
If I do git log I see the most recent commit is:
commit f69c36e28ea182523e99ee2e9a46db253cdaf8c2 Author: Burak Ä°nce burak.ince@linux.org.tr Date: Fri Feb 17 14:34:16 2017 +0200
I donât see the git commit hash that you mentioned in the recent logs. Are we talking about the same oclapi repository?
Then I do:
cd oclapi/django-nonrel/ocl/ docker-compose up
âŠlots of text scrolls by, eventually ending with:
ocl_api | Starting the server ocl_api | django-configurations version 0.8, using configuration âLocalâ ocl_api | Validating models⊠ocl_api | ocl_api | 0 errors found ocl_api | February 20, 2017 - 23:55:45 ocl_api | Django version 1.5.11, using settings âoclapi.settings.localâ ocl_api | Development server is running at http://0.0.0.0:8000/ ocl_api | Quit the server with CONTROL-C.
I then browse to http://localhost:8000/ and I see this:
(I havenât run the next few commands yet; are you already past this point?)
Please give more details about what instructions youâre following, what steps youâre taking, and what exact errors you see. As far as I know you shouldnât need to edit any of the docker-compose files, so I suggest that you do a clean checkout, run the first few commands, and report back any errors (use pastebin or github/gist to share long logs and error messages).
I am just starting this on a clean vm, and am getting this error in step 2. I have not attempted to get docker yet.
Just tried to use docker-compose up and this is what I got. It was at this point where we started to edit the files.
Edit: Also, do you know what version of docker-compose you are using?
Quick thought off the top of my head is that maybe you forked the repository a while ago and this you donât have the latest code.
(If you do âgit logâ what is the timestamp of the first entry you see?)
If that is true, and you donât have any meaningful code committed to your fork, I would delete your github fork and then fork from the original again, and then clone this.
-Darius (by phone)
I re-forked the repository and was able to add an upstream. However, still no luck with docker-compose. Thanks for the help!
I downloaded the latest version of docker-compose (1.11.2) and now am getting these errors when attempting to run docker-compose up. Iâm not sure what to do since it does not seem like you have to edit the docker files at all.
@andersont, not sure about the warnings, but the error indicates that the docker service is not running.
I ran dockerd, but then got a few errors so I am not sure if it actually did anything. However, I then attempted to run sudo docker-compose up and it worked. Thanks for the help!
I got to the very next step and got this issue. I havenât found much info on this particular error, and have not had much luck in fixing it.
@darius I just realized I did not reply to you or tag you in the previous message. Do you know what could be causing that error message or how to fix it? Iâve tried for a couple hours and havenât made much progress.
The error about no container found implies that the API docker container that you started in the previous step is not running.
Make sure that after you run docker-compose up you donât press control-C to close this. You would either need to do the next command in a new shell, or else run the previous command as docker-compose up -d so it runs in the background.
After that command, if you do docker ps you should see something like this:
MacBook-Pro-3:ocl djazayer$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
598ff8eb061c ocl_ocl_flower "bash run_flower.sh" 5 minutes ago Up 5 minutes 0.0.0.0:5555->5555/tcp ocl_flower
5c7e3f1cfd51 ocl_ocl_api "bash startup.sh" 5 minutes ago Up 5 minutes 0.0.0.0:8000->8000/tcp ocl_api
899bfbfe2538 ocl_ocl_worker "bash run_celery.sh" 5 minutes ago Up 5 minutes ocl_worker
f794c20a94b7 mongo:3.2.11 "/entrypoint.sh mo..." 5 minutes ago Up 5 minutes 0.0.0.0:27017->27017/tcp ocl_mongo
574a28d4c351 ocl_solr "docker-entrypoint..." 5 minutes ago Up 5 minutes 0.0.0.0:8983->8983/tcp ocl_solr
501c786103a8 redis "docker-entrypoint..." 9 days ago Up 5 minutes 0.0.0.0:6379->6379/tcp ocl_redis
The docker-compose exec ... steps should be run from the same directory, without stopping the prior docker-compose run (e.g. as I said before you either need to use -d or else a different shell).
Does this help?
Hi Darius!
So far weâve been using the README.md that is on the REST API. Weâve been using Ubuntu rather than a Mac so we didnât use instruction with the manual environment setup that we think you may have.
Weâve got docker-compose up to work and successfully logged in to http://0.0.0.0:8000/admin/authtoken/token/.
We donât know much about containers in docker and the next step requires us knowing the service name of a container⊠Do we continue forward with those instructions in the README?
Thank you so much, TIm and Abby
@ash082342, I am on a mac, but Iâm also following the âDocker Environment Setup (preferred)â instructions.
Yes, you should continue through a couple more steps in the README, especially you need to do the next couple about âinitialize look up values to MongoDBâ and âsync these values to Solrâ. Those commands should be correct as-written. Particularly, docker-compose exec ocl_api ... means ârun a command in the composed container called ocl_apiâ, which means this one.
After that, the OCL API should be running. The next step is to run the UI on top of that. Itâs in a different project: https://github.com/openconceptLab/ocl_web
The ocl_web instructions seem poorly organized (basically I think someone wrote updated instructions, but didnât feel confident to actually put them at the top of the file) so I would look at this section: https://github.com/openconceptLab/ocl_web/#updated-readme-for-dev-setup
@ash082342 and @andersont,
Weâve updated the documentation of the ocl_web project, so it should be correct now. You should still start here: https://github.com/OpenConceptLab/ocl_web/blob/master/README.md#updated-readme-for-dev-setup And note that you do not need to install postgresql to run this as a dev, because youâll use sqlite instead.
(Iâm going to be unavailable for the next 2 weeks, but if you ask any questions here someone should be able to help.)