-
Notifications
You must be signed in to change notification settings - Fork 185
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
Development composition fails to start with several errors #108
Comments
I encountered this issue on Windows. Are you on Windows? If so, there might be an issue with CRLF. On OSX (Intel), the datapusher api token is auto created but for windows, I had to add it to the .env file via one that was generated by the one on Mac:
Not sure why yet, but it allowed me to bring up all the svs. |
No, this is RHEL, but thank you and I will check to see whether a manually-generated token helps. |
I note that according to the following logs from the
|
Trying to chase this out and following the tip @iperezx just gave me, I find in the logs:
and in that script I see:
but
and the Docker log:
clearly shows that the appropriate env var contains the appropriate values. It's also not clear to me how |
I've changed the test in the |
Getting same issue with Ubuntu 22.04.2 LTS |
Now getting it on OSX(Intel). |
Do you see the same
section in the Docker logs and can you verify that the |
Yes. Same .env as what I was using before. |
It seems like Datapusher is not ready when ckan-dev is running the default entrypoint (https://github.com/ckan/ckan-docker-base/blob/main/ckan-2.10/dev/Dockerfile#L21). If I override the entrypoint in the docker-compose file:
Then attached to the running container:
Wait until ckan-docker-datapusher-1 outputs in the logs
Then run the default entrypoint script It runs as expected. Trying to figure out why its an issue with the new images. Waiting on datapusher to be in a healthy state (via docker-compose depends_on) doesnt work. |
I can confirm that @iperezx's commit in ckan/ckan-docker-base#38 enables the CKAN container to start for me. |
An alternative to not build from ckan-docker-base, one can also change the entrypoint to the following for ckan-dev:
|
@iperezx Got my dev environment to work as well, Thanks! |
Trying to start the development mode with
docker-compose.dev.yml
I get several seemingly-unrelated errors (and no startup). I include the full log run fromdocker compose up
as a gist, but I extract below what seem to be some of the relevant parts. The CKAN container just keeps trying to restart, only to run into the same problems. The backend containers for Redis, Solr, PostgreSQL and the DataPusher come up healthy.I hope there is an obvious mistake I am making?
I see
sh: image_view: unknown operand
reported over and over.This db error occurs over and over:
This DataPusher-related error also occurs several times:
and this error, which seems to be connected with db or maybe DataPusher access?
The text was updated successfully, but these errors were encountered: