Ozone Quickstart installation issues

Hi, great to see the progress with Ozone including Orthanc integration! I was interested to try it out on a local server, and just wanted to give some feedback of the steps I needed to take to get it working. The Ozone docs say “Only three commands in a terminal” but there are some pre-requisites and quirks that I wanted to share. Maybe I’m just too simple! But it might be good to include this information in the documentation.

  1. I started with a fresh Ubuntu 24.04 VM and followed the Quickstart command: curl -s https://raw.githubusercontent.com/ozone-his/ozone/main/scripts/install-stable.sh | bash /dev/stdin Failed with error message: The JAVA_HOME environment variable is not defined correctly, this environment variable is needed to run this program.

  2. Installed Java with sudo apt install default-jre-headless and ran quick start command again - success.

  3. Ran cd ozone/run/docker/scripts/ and ./start-demo.sh Failed due to utils.sh: line 204: docker: command not found - docker not installed. I installed docker following the usual docker directions. Then ran ./start-demo.sh again. Failed due to docker permissions error.

  4. I ran sudo ./start-demo.sh, it then failed with error: utils.sh: line 220: /tmp/project_name.txt: Permission denied I looked in utils.sh, line 220 refers to storing a file in /tmp which seems to be owned by root I had to run sudo chmod -R o+rw /tmp and then rm /tmp/project_name.txt

  5. Finally, running sudo ./start-demo.sh was successful.

Perhaps the Quickstart documentation could be updated to say that java and docker are prerequisites, the command needs to be run as root, and the issue with /tmp/project_name.txt could be fixed in utils.sh? This might make it easier for less competent people like me to experiment…

Thanks again for the great project!!!

5 Likes

Thanks for the feedback @andylinton . Indeed we are missing the prerequisite for the Quick Start guide (some are present in other places in the documentation), which are Maven (so, Java) and a recent version of Docker / Docker Compose.

Let us update that.

Note that we are also actively writing docs and there is some changes coming soon, in particular for the Implementer Docs. Hopefully they’ll be more accurate and helpful.

1 Like

Please, let us know how your testing goes from there. Additionally, you can reach out on the #ozone channel for direct support.

Great, thanks! I’m looking forward to testing it out further.

1 Like