Issues with ROR Docker Setup

[Søren Vidmar]

Dear ROR Technical Team,

I’ve been using the ROR API Docker setup previously, based on the README instructions, and it was working great. However, after following the same steps on a new machine recently, I’ve encountered issues and the process no longer works as expected.

The following specific issues have arisen:

Elasticsearch Container Health Status: When I run the Docker containers, the Elasticsearch container starts but is marked as “unhealthy.” This prevents the full ROR stack from functioning correctly. Also I am having trouble indexing the zip file containing the data, despite following the instructions in the readme. 

Are there any recent updates or changes to the setup process, indexing, or data dump, not covered by the readme? Not very experienced with Docker, so tried to get help from various LLM's but alas :-) 

Any help would be greatly appreciated. 

Best regards,

Søren

[Adam Buttrick]

Hi Søren,

Sorry to hear you're running into issues on the new machine!

There haven't been any recent changes to the Docker setup or indexing process described in the README that would result in the Elasticsearch container becoming unhealthy after working previously.

The problem you're describing can point at insufficient disk space being available to the container. The Elasticsearch setup requires a good amount of available disk space and can become unhealthy if it hits disk usage limits (which are also determined by the total available space on your device).

Could you please check the available disk space on your new machine, as well as try upping the limit of the space allocated to Docker Desktop (Settings -> Resources -> Advanced -> Disk usage limit) if you're using that? Ensuring you have ample space available and configured might resolve the unhealthy container status.

Thanks,
Adam

[Søren Vidmar]

Hi Adam

Thank you for the quick reply!

I checked the disk space, and there was plenty available on both my machine and for Docker. While I wasn’t sure what caused the issue, I managed to resolve it by starting fresh—reinstalling Docker and clearing all files, containers, and images related to ROR. Looks like the problem was something on my end—probably a “tech gremlin” that needed a good reset! 😅

It’s running beautifully - and super fast- now 🥳

Best regards,

Søren