Closed ivanDvernitsky closed 6 months ago
I'm unable to recreate this error. Seems a couple of issues going on here.
The first one is the ckan, -c /srv/app/ckan.ini db init
command from the prerun.py
setup when the CKAN container starts. Are you able to attach to the running CKAN container and execute the ckan-c /srv/app/ckan.ini db init
command from the shell? It should error but may give more information
I'm closing this issue because I've found a stabla way to run CKAN in a development mode
I've been trying to get CKAN running on my MAC OS with M1 chip. After doing
docker compose build
and thendocker compose up -d
got CKAN to work. But on the next attempts to start the container it fails. In particular when starting the container with 'docker compose up' or ''docker compose up -d' - NGINX container exits right away. Sometimes it helps to just manually start it with Docker Desktop, but most of the times I can't access CKAN and see "-Internal Server Error:" message in the browser.Trying to start container group in the Docker desktop it takes forever to start for NGINX, and it never does.
In the development mode NGINX also exits right away and I get a 404 not found message from it.
If I manage start NGINX through Docker desktop, Datapusher container comes up as unhealthy.
dd670ab3b287 ckan/ckan-base-datapusher:0.0.20 "sh -c 'uwsgi --plug…" 18 hours ago Up 2 minutes (unhealthy)
Here are the log records: