I created a very simple issue and PR to open the Payara admin console port in the dev_dataverse container for the dev docker-compose file:
https://github.com/IQSS/dataverse/pull/9478
This is related with a conversation we had on the app container PR: https://github.com/IQSS/dataverse/pull/9439#issuecomment-1473774464
Approved! Thanks!
Guillermo Portas said:
I created a very simple issue and PR to open the Payara admin console port in the dev_dataverse container for the dev docker-compose file:
https://github.com/IQSS/dataverse/pull/9478
This is related with a conversation we had on the app container PR: https://github.com/IQSS/dataverse/pull/9439#issuecomment-1473774464
for dev exposing the console is fine; but in the past couple of years we've had an installation or two unintentionally expose the console (and all higher listening ports) because that's what Docker containers do. it's truly up to the implementing party; but perhaps a note cautioning about exposing such things.
Yikes. Was the username and password still admin/admin? :sweat_smile:
@Don Sizemore I added a suggestion and assigned @Guillermo Portas to take a look. If have better wording, please help! Thanks! :smile:
I agree, @Don Sizemore . This is for development purpose.
I personally find the console useful when testing new configurations and deployments, as a visualization tool. When it comes to applying changes to the server, I recommend using the asadmin commands... So, for productive usage, I would not open it.
The username and password admin/admin comes from the base image Dockerfile. See: https://github.com/IQSS/dataverse/blob/develop/modules/container-base/src/main/docker/Dockerfile#L45
When we evolve the image for productive use, I would obviously make these parameters configurable! @Philip Durbin
I think this is resolved now, isn't it?
Oliver Bertuch has marked this topic as resolved.
Last updated: Oct 30 2025 at 05:14 UTC