-
Notifications
You must be signed in to change notification settings - Fork 75
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
configure-database.sh failure #38
Comments
#39 fixes the issue with the atom.sql. For the rest, what version of docker-compose and docker do you have? |
Thanks for the help. I'm familiar with Docker but haven't used docker-compose before. See below:
|
since you have the latest version, that is not issue. If you had used docker-compose version 1.2.0 try https://docs.docker.com/compose/install/#upgrading , if not remove all of your containers |
Ah, this was caused by my running docker-compose on a shared filesystem (I use a VM which mounts my ~/opencog dir from the host, and all repos are cloned into that). For some reason this led to permission issues with the postgres data dir. So running from my home folder, coupled with #39, seems to fix it. Thanks! |
I'm following the steps in the opencog folder readme. After I call
this is what I get from the configure-database.sh script:
The atom.sql file is now in the atomspace project, but I don't know what causes the db address issue.
Then, after exiting the container, subsequence calls to docker-compose run fail:
The text was updated successfully, but these errors were encountered: