Mark Wilkinson (Dec 04 2024 at 07:50): Mark Wilkinson (Dec 04 2024 at 07:50):As suggested by Philip, I have moved my reports from GitHub to here :-)
Philip, you suggested that I try running the demo (https://guides.dataverse.org/en/6.4/container/running/demo.html). I did so. The first step (running docker-compose up, with no "demo" folder) was fine. Dataverse came up and I could login. The second step failed. Creating a "demo" folder with the init.sh script, then docker-compose up results in an endless cycle of:
bootstrap | 2024-12-04T07:49:28Z INF [HTTP] Checking the http://dataverse:8080/api/info/version ...
bootstrap | 2024-12-04T07:49:28Z ERR Expectation failed error="the status code doesn't expect" actual=404 expect=200
bootstrap | 2024-12-04T07:49:36Z INF [HTTP] Checking the http://dataverse:8080/api/info/version ...
bootstrap | 2024-12-04T07:49:36Z ERR Expectation failed error="the status code doesn't expect" actual=404 expect=200
until the timeout is reached.
Suggestions?
thanks!
Philip Durbin 🚀 (Dec 04 2024 at 11:52):@Mark Wilkinson hi! Thanks for trying our containers! I'm sorry to hear you're having problems. If that /api/info/version endpoint failed there's a good chance the Dataverse war file could not be deployed to the Payara app server. Can you please provide more of the logs from the "dataverse" container so we can see what went wrong?
Philip Durbin 🚀 (Dec 05 2024 at 14:15):You could try something like this, for example:
docker logs dataverse > logs.txt 2>&1
Also, I forgot to mention this but we have a meeting about containers every week. The next one is in 15 minutes! :sweat_smile: Please feel free to join sometime! https://ct.gdcc.io
Mark Wilkinson (Dec 09 2024 at 07:55): Mark Wilkinson (Dec 09 2024 at 07:55):Philip Durbin 🐉 said:
Also, I forgot to mention this but we have a meeting about containers every week. The next one is in 15 minutes! :sweat_smile: Please feel free to join sometime! https://ct.gdcc.io
If I have to add another meeting to my calendar I will scream! LOL!
Philip Durbin 🚀 (Dec 09 2024 at 12:21):@Mark Wilkinson thanks! This error is definitely fatal but I'm not sure why you're seeing it:
Caused by: org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException: Migration V4.11__5513-database-variablemetadata.sql failed
----------------------------------------------------------
SQL State : 42P01
Error Code : 0
Message : ERROR: relation "datavariable" does not exist
Location : db/migration/V4.11__5513-database-variablemetadata.sql (/opt/payara/deployments/dataverse/WEB-INF/classes/db/migration/V4.11__5513-database-variablemetadata.sql)
Line : 4
Statement : -- universe is dropped since it is empty in the dataverse
-- this column will be moved to variablemetadata table
-- issue 5513
ALTER TABLE datavariable
DROP COLUMN if exists universe
I'm curious about why you're seeing it but practically speaking I'd like to get you unblocked so you can continue with your setup of Dataverse.
What if you move the data directory aside and try again? Instead of deleting it in case we want to try to reproduce the problem later, I mean.
And then try again?
Mark Wilkinson (Dec 09 2024 at 12:41):That works! I will continue following the tutorial! thanks!
Philip Durbin 🚀 (Dec 09 2024 at 13:23):Phew! :sweat_smile: Go, go, go! :tada:
Mark Wilkinson (Dec 27 2024 at 10:36):Hi Philip! Coming back to this... is there anything I will be missing if I am not able to get the init.sh script to run? Or will Dataverse be fully functional, back-uppable, etc.? If everything is OK, I will start to move into Production :-)
Mark Wilkinson (Dec 27 2024 at 11:24):Well... the previous question doesn't matter in any case! I switched to my production server, and had exactly the opposite result: I could NOT bring up the demo server without the init.sh script! It ran, and then everything was fine!
So the new question is: should I remove the init.sh script now that it has been run once? Or just leave it there?
Philip Durbin 🚀 (Jan 08 2025 at 14:56):@Mark Wilkinson the init.sh script should only run once. It's fine to leave in place, as part of the configbaker image. When the configbaker image runs it should detect if Dataverse has already been configured or not and only run the init.sh script if Dataverse hasn't been configured.
Philip Durbin 🚀 (Jan 08 2025 at 14:58):Regarding production, as we say at https://guides.dataverse.org/en/6.5/container/running/production.html we are still working on tagging images so that you can be locked to a specific image (e.g. 6.4 or 6.5). We also plan to add more docs. Please keep the feedback coming! We want people with an eye toward production use to let us know what we've missed! :sweat_smile:
Last updated: Oct 30 2025 at 05:14 UTC