Postgres client is still on v14 after upgrade
Summary
(Summarize the bug encountered concisely) The defectdojo-django image is using the pg14 client after it was attempted to be upgraded to pg15.
Steps to reproduce
(How one can reproduce the issue - this is very important) In the Dockerfile in this repo you can see that the pg14 client binary is being copied over. In the Dockerfile of the postgresql:15.0 image you can see that only pg14.5 is being made available.
You could also run the container locally with an interactive shell, and run pgsql -v
to get the installed version.
What is the current bug behavior?
(What actually happens) The postgres client available in the v15 tag is only the v14.5 client registry1.dso.mil/ironbank/opensource/postgres/postgresql:15.0
What is the expected correct behavior?
(What you should see instead) The image tagged postgresql:15.0 in Iron Bank should have a v15 client binary available in it.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) !40 (comment 886735)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem) Correct the postgresql:15.0 Dockerfile. This merge this MR !40 (closed).
Tasks
-
Bug has been identified and corrected within the container