Gwenaël Doux (May 27 2025 at 07:23): Gwenaël Doux (May 27 2025 at 07:23):I recently encountered a recurring issue when running the Docker demo. I was able to run version 6.2 without any problems, but when I tried to update to 6.6, I started getting a 404 response from Dataverse.
I tried several of the tips you shared here, including increasing the timeout to 10, but none of them resolved the issue. I also removed all containers and re-downloaded the original docker compose‧yml file, but the problem persisted.
The only log line I found in the configbaker logs was:
Checking the http://dataverse:8080/api/info/version ... curl: (6) Could not resolve host: dataverse
I also asked ClaudeAI for help and described the issue. After a bit of back and forth, it suggested that the problem might be related to the order in which the Docker services are started.
So I tried the following steps:
docker compose up -d postgres solr smtp dv_initializer solr_initializer
sleep 10
docker compose up -d dataverse
# look at the logs until everything has finished booting up
docker compose up -d bootstrap register-previewers previewers-provider
Apparently, the issue was indeed related to the service start order. I'm not sure what changes could be made to the setup to prevent this, but if anyone else encounters the same error, these steps might help.
Philip Durbin 🚀 (May 27 2025 at 13:19):Hmm, we did add service_completed_successfully over in the frontend repo: https://github.com/IQSS/dataverse-frontend/pull/180
Philip Durbin 🚀 (May 27 2025 at 13:19):I'm not sure if it would help or not. You're welcome to try!
Philip Durbin 🚀 (May 27 2025 at 13:19):Could not resolve host: dataverse sounds like it's not on the same network. :thinking:
Last updated: Oct 30 2025 at 05:14 UTC