-
Notifications
You must be signed in to change notification settings - Fork 152
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
Won't start up #74
Comments
I think you need to remove all containers, images, networks and volumes...Also run a The screenshot below is how the database processes in the running db container should look like |
@kowh-ai I already did that several times, actually it is a brand new VPS. |
I had the same problem. The above mentioned solution by kowh-ai worked for me. |
I was dealing with this issue, and was able to resolve it by manually executing the To do so you'll need to enter the db container in interactive mode: docker exec -it db bash Then cd docker-entrypoint-initdb.d/
ls
10_create_ckandb.sh 20_create_datastore.sh 30_setup_test_databases.sql Then execute both scripts: . 10_create_ckandb.sh
. 20_create_datastore.sh The needed roles and databases will be created. You should then exit the db container and restart both containers. The ckan container will now be able to connect to the db. The solution provided by @kowh-ai is most likely more correct, but if nothing else works, this worked for me. |
@kowh-ai , @iag-ggos and @Perla-Al-Haddad, thanks for you help, it seems like your solution solved the DB issue, but it still presents another couple of execution errors: This one in what looks like a 'ckan' script:
And this one in a 'wsgi.py' script:
And finally:
|
Again, I think you need to remove all containers, images, networks and volumes...Also run a |
@kowh-ai, I swear I ran |
Adding one missing puzzle piece: it might be necessary to remove volumes as well. The database is created in a docker volume and if you misconfigured it during your first run, it remains. Named volumes don't seem to be removed even with
... and then remove those. This will obviously destroy all the data within, so first make sure there's nothing worth keeping.
Then start ckan again with a vanilla |
After following the instruction in the Readme, I keep getting
password authentication failed for user "ckandbuser"
and"ckandbuser" role does not exist
.In the end, Docker compose aborts it and it never runs with the message
dependency failed to start: container ckan is unhealthy
.The text was updated successfully, but these errors were encountered: