ckan / ckan/ckan-docker

Recreating another CKAN instance (after the default is running successfully) doesn't work

Open
#103 9 comments 0 reactions 1 assignee Claimed by @kowh-ai View on GitHub
Dominant language
Shell
Stars
151
Forks
279
PR merge metrics
No merged PRs in 30d

Description

Hello!

I managed to get a CKAN instance running successfully on `localhost:8443` (the default). However, subsequent attempts to launch an instance fail.

I have tried changing the ports, container names, and service names in the `.env` and `docker-compose.yml` file for `solr`, `datapusher`, `nginx` as well as `redis`, but I keep getting a `dependency failed to start: solr_new is unhealthy`.

When I do a `docker compose exec solr_new env`, I still see the default values; my updates are not reflecting for the new container. Similarly for `datapusher_new`. I have found the config files for the two in their respective containers (`datapusher_settings.py` and `jetty.xml`) that do contain the ports that I probably need to change, but they're read-only.

How do I resolve this, and get a container to run successfully when there already is a CKAN instance running?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.