Hi @Philip Durbin .
I hope all is well. I've been tasked with creating a new instance of Dataverse.
This time around I was looking to go through the installation process by using a docker container.
Is the latest version (6 I think?) already featured in the dataverse-docker?
If not, is it possible to install the existing version and then upgrade it to the latest?
I'm not a super technical guy so I'm trying my best :)
Hi! What are you doing in a little under 3 hours? :grinning: https://time.is/compare/0930_05_Oct_2023_in_Boston
I ask because I'm happy to put this on the agenda for our weekly container meeting: https://ct.gdcc.io
dataverse-docker is community supported, primarily by @Slava Tykhonov . I'm not sure if it has been updated to Dataverse 6 yet or not.
It seems to be using 5.13.allclouds from https://hub.docker.com/r/coronawhy/dataverse/tags
I'm not sure how upgrades work within the dataverse-docker world.
Philip Durbin disse:
I ask because I'm happy to put this on the agenda for our weekly container meeting: https://ct.gdcc.io
I'll be glad to join you :)
I've found the link :)
Great!
Is this installation for demo purposes? Or production?
Philip Durbin disse:
Is this installation for demo purposes? Or production?
It will be for production. But at a very small scale.
Ok, when we visited @Jin Kim and his institution they were excited about using Docker but I steered them toward a traditional install using dataverse-ansible by @Don Sizemore - https://github.com/GlobalDataverseCommunityConsortium/dataverse-ansible
That was in February. Not much has changed in my thinking for production installations.
But some people like living on the edge a bit more. :grinning:
The core team is working on container support. Our docs are here: https://guides.dataverse.org/en/6.0/container
But it's early days. Very useful for development. Not ready for production.
I guess this is a pretty good summary: https://guides.dataverse.org/en/6.0/developers/containers.html
@thejmfc thanks for joining! Here's a recording of the container meeting: https://harvard.zoom.us/rec/share/8hdCr5MXA5C0DqyKD4ZAVT68Ujbjv5M-zX2TSeyNNZWIGObFnndSFzzUkS55WUoS.S23mmocPC9w2IzMg
And the notes: https://docs.google.com/document/d/1GcHeggd4A6qdKkyYaC1Q1KuYCZkm0SHHVT5aCLsje9U/edit?usp=sharing
Please keep the questions coming!
Hi @thejmfc , we're testing Dataverse 6 in Dataverse-docker. Coming soon! @Thomas van Erven is working on it.
Small clarification there; I'm just working directly off the dataverse repo including configbaker (but logically replicating that setup to dataverse-docker should be "simple"; just copy created files and possibly the base image for dataverse to make it war-less). What might be a bit more work is copying/replicating all the .env options that dataverse-docker supports (not just the JVM ones); I'm more of a fan of creating a base image and packaging that to become a dataverse-docker image. Ideally you want to preserve backwards compatibility in these instances.
So far I'd say the alpha image represents a stable working image, I can work from there for a port, if desired.
It was always on the agenda that we look into transferring the itsy bitsy scripty thingies that dataverse-docker uses for configuration different aspects into the main repo. Basically: make the installer scripts much more modular, so we can better reuse them.
(I hate that there are two different installers - maintenance in one place is much less work for everyone)
Thomas van Erven said:
So far I'd say the alpha image represents a stable working image, I can work from there for a port, if desired.
You might want to use the develop branch based unstable for now. My PR to configure all the upload/tempfile locations just has been merged and will be of great service within containers... :wink:
Thanks for the headsup; I'll switch it over on our env. Any particular commit I might pin to?
Edit: I'll check the repo, since you've just had a merge it should be easy to identify.
Last updated: Oct 30 2025 at 05:14 UTC