Skip to content

Conversation

ImreSamu
Copy link

@ImreSamu ImreSamu commented Oct 9, 2025

This pull request updates gosu from version 1.16 to 1.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):

$ trivy image --ignore-unfixed supabase/postgres:17.5.1.041-orioledb
...
usr/local/bin/gosu (gobinary)
Total: 69 (UNKNOWN: 0, LOW: 2, MEDIUM: 30, HIGH: 34, CRITICAL: 3)

[5] docker-library/postgres@a243375

Update gosu from version 1.16 to 1.19 in Dockerfile-15, Dockerfile-17, and Dockerfile-orioledb-17.

This change aligns the Docker images with the official Docker Postgres image,
which recently upgraded to gosu 1.19. Staying consistent with the upstream
helps reduce potential security findings and maintain compatibility with
the official base images.

A Trivy scan on the previous image reported several medium to critical
issues in the older gosu binary. Updating to the latest version helps
minimize these potential risks.

No functional changes beyond the version update.
@ImreSamu ImreSamu requested review from a team as code owners October 9, 2025 21:53
@samrose
Copy link
Collaborator

samrose commented Oct 10, 2025

Thanks for this, we're going to look into this ASAP

Copy link
Collaborator

@samrose samrose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not requesting specific changes yet. But we'll look into this and resolve ASAP. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants