I just thought I'd kick off a topic to discuss and issued @Vera Clemens opened: Feature Request/Idea: Add psql to the configbaker image #10487
Sure, go ahead and create a PR
I would like to point out though that a cleaner and more testable solution would be to make Dataverse pick up the procedures via Flyway
Obviously that is a lot more effort...
Yeah, that sounds like a new topic :sweat_smile:
Adding psql should be straighforward, right? Just add to an existing list of apt-get install packages or something?
It's Alpine so it will be "apk", but yes, more or less straightforward
Might be nice to have a little helper script that adds the connection options for you to sane defaults so you don't have to deal with that in simple cases
ARG APK_PACKAGES="curl bind-tools netcat-openbsd jq bash dumb-init wait4x ed" at https://github.com/IQSS/dataverse/blob/v6.2/modules/container-configbaker/Dockerfile#L24
thanks!
If people feel like we should add another ARG to include custom packages during build time, that's doable
(So you would use a Maven property in your build pipeline to add more packages)
Sure, but what do you think? Separate issue and PR?
Don't look now, @Johannes D made a PR: Added postgresql-client to the list of installed apk packages #10488
Is it also possible to get the package in Dataverse image? This allows you to run certain custom scripts.
"postgresql-client"
or is there something against it?
@Benedikt sounds fine to me. Please feel free to create an issue and a pull request.
https://github.com/IQSS/dataverse/pull/10546
Thanks!
@Benedikt hi! @Oliver Bertuch @Thomas van Erven and I are discussing this during the weekly call and we're wondering if adding psql to the base image is necessary. It adds more exposure, possible security risks, and psql could be run from configbaker or the postgres image. Can you please say some more about your use cases? Thanks!
Thanks for talking this out just now on the call.
I have closed it, and I understand why it should not be intrgated. My question is why do you have wget and curl in there?
If you want to keep it small and clean, then you can do a bit more. Or is there a reason for this?
Hmm, good question, where to draw the line.
Should we add a comment above the ARG PKGS line? To provide some guidance?
I think what's relevant (as well) is what's the dependency chain for those packages and how much of that is provided by the base image? Are we going out of our way to include them (hence unnecessarily increasing exposure) or is it a really minor detour?
Last updated: Oct 30 2025 at 05:14 UTC