I'm trying to figure out what could be wrong when I try to spin up an evaluation instance using instructions in Dataverse container setup. Somehow the docker compose up does not make progress past getting Payara up and running, so when I go to localhost:8080, I get the "Hello from Payara - your server is now running" page and nothing else. I increased the bootstrap timeout value to 20 minutes, but it did not help.
@mjlassila hmm, could you please post output from the "dataverse" container? It sounds like the war file wasn't properly deployed.
I believe the container is called "dataverse" (if not, you can check with docker ps). So docker logs dataverse should show the output.
Here's the output I got by redirecting docker logs dataverse to the file docker-dataverse.log. Additionally there's some likely relevant output displayed in terminal when I run docker compose up:
dataverse |
dataverse exited with code 0
dataverse | /opt/payara/scripts/entrypoint.sh: line 15: /opt/payara/config/pre-boot-commands.asadmin: Permission denied
dataverse | /opt/payara/scripts/entrypoint.sh: line 17: /opt/payara/config/post-boot-commands.asadmin: Permission denied
dataverse | [Entrypoint] running /opt/payara/scripts/init_1_generate_deploy_commands.sh
dataverse | post boot commands already deploys /opt/payara/deployments/dataverse
dataverse |
dataverse | [Entrypoint] running /opt/payara/scripts/init_1_generate_devmode_commands.sh
Permission denied. Hmm
Are you on Windows? If so, did you clone the repo from a Linux terminal?
I'm running MacOS 14.4
Huh, I'm on MacOS too
Do you happen to have Java and Maven installed? If so, you could try this developer-oriented version: https://guides.dataverse.org/en/6.2/developers/dev-environment.html#quickstart
I'm not sure why you're getting that permission error.
@mjlassila we just talked about this during (#containers > weekly meeting ) but no one had any ideas off hand. Any progress?
I finally managed to get this working using docker compose by tweaking my Docker setup. I'm using colima as my Docker runtime and the latest version was using vz for virtualization in M3 Macs, instead of better supported QEMU and 9p for filesystem mounts.
When I got Dataverse up, the final hurdle was to get Solr to initialize. From the log I saw error that schema.xml was not found in /var/solr/data/collection1 in the solr container. When I copied schema.xml to the [directory-with-docker-compose]/data/solr/data/data/collection1 I got Solr up and running.
Interesting. Should we add any of this to our documentation? Would you want to make a pull request?
I'm glad you got it working! :tada:
Last updated: Oct 30 2025 at 05:14 UTC