chore(docker): bump gosu to 1.19 #1832
Open
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates
gosu
from version1.16
to1.19
in the following Dockerfiles:Dockerfile-15
Dockerfile-17
Dockerfile-orioledb-17
The official Docker Postgres image has already upgraded [5] to gosu 1.19 [1],
and this change keeps these images consistent with the upstream base.
Using the latest
gosu
release [2] also helps reduce potential security findings reported by image scanners.For example, a recent local Trivy scan [3] reported several medium to critical issues in the older
gosu
binary.No functional changes beyond the version update.
References
[1] Upstream Postgres Dockerfile (gosu 1.19):
https://github.com/docker-library/postgres/blob/master/Dockerfile-debian.template
[2] gosu 1.19 release notes:
https://github.com/tianon/gosu/releases/tag/1.19
Additional releases (1.17–1.19): https://github.com/tianon/gosu/releases
[3] Trivy scan example (old gosu 1.16 binary):
[5] docker-library/postgres@a243375