Skip to content
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

Closed
pennachin opened this issue Jun 29, 2015 · 4 comments
Closed

configure-database.sh failure #38

pennachin opened this issue Jun 29, 2015 · 4 comments

Comments

@pennachin
Copy link
Member

I'm following the steps in the opencog folder readme. After I call

docker-compose run --service-ports dev

this is what I get from the configure-database.sh script:

opencog@fa93844c7bf9:~$ ~/configure-database.sh
psql: could not translate host name "db" to address: Name or service not known
psql: could not translate host name "db" to address: Name or service not known
cat: /opencog/opencog/persist/sql/atom.sql: No such file or directory
psql: could not translate host name "db" to address: Name or service not known
psql: could not translate host name "db" to address: Name or service not known
psql: could not translate host name "db" to address: Name or service not known
cat: /opencog/opencog/persist/sql/atom.sql: No such file or directory
psql: could not translate host name "db" to address: Name or service not known

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:

cassio@opencog:~/opencog/docker/opencog$ docker-compose run --service-ports dev
Starting opencog_postgres_1...
Cannot start container 621523308b4c0f26547e18c17f9c57469463f126148dba879f806add7d01f0d0: Cannot link to a non running container: /opencog_postgres_1 AS /opencog_dev_run_2/db
@amebel
Copy link
Contributor

amebel commented Jun 29, 2015

#39 fixes the issue with the atom.sql.

For the rest, what version of docker-compose and docker do you have?

@pennachin
Copy link
Member Author

Thanks for the help. I'm familiar with Docker but haven't used docker-compose before. See below:

cassio@opencog:~/opencog/docker/opencog$ docker --version
Docker version 1.7.0, build 0baf609
cassio@opencog:~/opencog/docker/opencog$ docker-compose --version
docker-compose version: 1.3.0
CPython version: 2.7.6
OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014

@amebel
Copy link
Contributor

amebel commented Jun 30, 2015

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 docker rm -v $(docker ps -aq), ofcourse you can cherry-pick them to.

@pennachin
Copy link
Member Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants