I have been try the latest code indataverse-docker and it failed to boot dataverse correctly. I find in the commit record that 6.2 has been revert, does that mean it is not ready yet
@Slava Tykhonov might be able to help you with dataverse-docker
@link89 you can also try the upstream images. Please see https://guides.dataverse.org/en/6.3/container/running/demo.html
I am thinking about a better way to implement docker deployment and here is some idea:
instead of providing a full functional dataverse docker image,
maybe it's better to provide a image with all artifact included,
and then the end user can just write a Dockerfile based on this image and use dvinstall script to config the service and run.
You are of course free to do such a thing, no one will stop you.
That said, for the past 5 years, I have been working on improving Dataverse to make it a near cloud native application. It's still a work in progress.
What we have so far is documented in the guides Phil linked to. If you're interested in joining forces, feel free to join the Containerization Working Group. There's a channel at #containers where we discuss activities and the homepage at https://ct.gdcc.io has all our recordings and activities.
I would like to after I success to run it. It looks like both 6.2 and 6.3 have unsolved bug, which version do you suggest to run in production?
By the way, what's the main reason that make dockernize so hard to do? I am keep blocking when running install.py in both docker and non-docker environment.
Now I see what happens. It's proxy!
The global proxy has been setup to install dependency and the setup-all.sh make use of curl to fire requests, which will respect the proxy setting.
Like Oliver says, we'd be very happy to work with you!
Last updated: Nov 01 2025 at 14:11 UTC