Renee L. (Jun 05 2026 at 18:14): Renee L. (Jun 05 2026 at 18:14):Trying to connect to http://localhost:8080/ and http://dataverse:8080/api/info/version results in ERR_CONNECTION_REFUSED.
Running netstat -nlt | grep 5432
gets the following response:
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN
tcp6 0 0 ::1:5432 :::* LISTEN
I suspect this issue might be due to having an installation of samvera that was already using postgres prior to installing dataverse.
Philip Durbin 🚀 (Jun 05 2026 at 18:15):@Renee L. hi! You found your way to Zulip! I haven't checked your ticket in a while, sorry.
Philip Durbin 🚀 (Jun 05 2026 at 18:17):Is this on Linux, Mac, or Windows, please?
Renee L. (Jun 05 2026 at 18:18):It's on Linux.
Philip Durbin 🚀 (Jun 05 2026 at 18:24):And are you evaluating Dataverse? Something like this: https://guides.dataverse.org/en/6.10.1/container/running/demo.html
Renee L. (Jun 05 2026 at 18:26):Yes, although I was also following steps from https://guides.dataverse.org/en/latest/developers/dev-environment.html because I needed to install Java 21 and Maven.
Philip Durbin 🚀 (Jun 05 2026 at 18:26):Ah, that makes sense.
Philip Durbin 🚀 (Jun 05 2026 at 18:27):Hmm, actually, for https://guides.dataverse.org/en/6.10.1/container/running/demo.html you should only need Docker. :thinking:
Philip Durbin 🚀 (Jun 05 2026 at 18:28):Can you please give this a try? https://guides.dataverse.org/en/6.10.1/container/running/demo.html#quickstart
Renee L. (Jun 05 2026 at 18:41):I saw the following error messages:
dv_initializer exited with code 1
solr_initializer exited with code 1
Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint postgres (887dc6ab81c1ff565c7720544e9b3133fea9192d956f6cecbee
c566f858640f4): failed to bind host port 0.0.0.0:5432/tcp: address already in use
Philip Durbin 🚀 (Jun 05 2026 at 18:42):Ok, and you need to keep the old instance of Postgres running, right? You can't just stop it? Samvera is using it?
Renee L. (Jun 05 2026 at 18:42):Yes, I need the old instance of Postgres too for Samvera.
Philip Durbin 🚀 (Jun 05 2026 at 18:44):Let's see, I think we'll need to change which port postgres is running on. I should be here in your file: https://github.com/IQSS/dataverse/blob/v6.10.1/docker/compose/demo/compose.yml#L117
Philip Durbin 🚀 (Jun 05 2026 at 18:44):And up around here we'll need to add DATAVERSE_DB_PORT with whatever new port you pick: https://github.com/IQSS/dataverse/blob/v6.10.1/docker/compose/demo/compose.yml#L13-L15
DATAVERSE_DB_PORT is described (sort of) at https://guides.dataverse.org/en/6.10.1/installation/config.html#basic-database-settings
Philip Durbin 🚀 (Jun 05 2026 at 18:45):Does that make sense? Those two edits?
Renee L. (Jun 05 2026 at 18:51):That makes sense. I think that second edit is what I've been looking for...
Philip Durbin 🚀 (Jun 05 2026 at 18:54):Sure, and it's not explained well in the guides. Please feel free to open an issue about this at https://github.com/IQSS/dataverse/issues
Philip Durbin 🚀 (Jun 11 2026 at 15:31):@Renee L. hopefully the above worked for you. This morning @Oliver Bertuch brought up the fact that an easier workaround might be to keep Dataverse (and Postgres) using the standard postgres port but make it so a different port is exposed to the host (a laptop, in my case, but perhaps a server for you) or not exposed at all. Here's the recording, notes, and the docs we looked at: https://docs.docker.com/reference/compose-file/services/#ports
Last updated: Aug 18 2026 at 08:27 UTC