-
Notifications
You must be signed in to change notification settings - Fork 176
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
Recreating another CKAN instance (after the default is running successfully) doesn't work #103
Comments
Sounds like something got messed up along the way. Are you able to stop all containers and remove all images, networks, volumes and containers plus run a |
I am facing the same error, even after a My workflow is this (after successfully running a clone of this repository as is):
However, after a I did think of perhaps creating new config files (such as No luck so far unfortunately! |
Are you able to post (here) all of the logs during the startup? |
I'm posting the logs for the
|
Is that the end of the Solr log?...the next lines should be: |
This is the entire output from the logs for my solr container! I changed the ports for it in the |
Just as an add-on... if I already have an instance of CKAN running successfully (with the defaults from this repository), and I need to run another instance from the same machine... what steps do I need to take? My assumption was that I needed to change the ports being used in the Is there something I'm missing out on? |
Try it and see...it should be self explanatory...different container names definitely...ports can be the same if the container name (ie: hostname) is different |
I changed the port numbers to their defaults, they're all the same except for the
I have changed the container name for |
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
anddocker-compose.yml
file forsolr
,datapusher
,nginx
as well asredis
, but I keep getting adependency 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 fordatapusher_new
. I have found the config files for the two in their respective containers (datapusher_settings.py
andjetty.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?
The text was updated successfully, but these errors were encountered: