Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Review unnecessary Python packaging tools in PostgreSQL image

Aperta
  • Qualcosa non va?
#524 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

@benispeti ci sta già lavorando.

Dal 11/10/2026.

  • #527 di @benispeti — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker, postgresql, python
Ambito
databases, infrastructure

Direzione di ricerca

Start by locating the image build definitions for ghcr.io/cloudnative-pg/postgresql:17.10-system-trixie and identify how Python packages are installed. Check supported backup, restore, and operational workflows for uses of pip, setuptools, and wheel; the issue does not name specific files or tests. Done means removing tools that are not required, or documenting why they remain, while preserving those workflows and verifying the resulting image's SBOM.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Description
Our SBOM scan identified Python packaging tools in the following PostgreSQL image:

ghcr.io/cloudnative-pg/postgresql:17.10-system-trixie

Reported Packages
Package Version(s)
pip 25.1.1
python3-pip 25.1.1+dfsg-1
setuptools 78.1.1
python3-setuptools 78.1.1-0.1
wheel 0.45.1, 0.46.1
python3-wheel 0.46.1-2

Concern
Package installation and build tools are generally unnecessary in a production runtime image once dependencies have been installed. Where unused, retaining them increases image size and the number of components requiring vulnerability monitoring.

Multiple reported wheel versions also warrant checking whether they correspond to separate installations or bundled metadata.

Expected Behavior
The runtime image should retain only Python components needed for supported PostgreSQL, backup, and operational workflows. Build-only tooling should remain outside the final image where practical.

Requested Investigation

  • Confirm whether pip, setuptools, and wheel are required by supported runtime workflows.
  • Remove unnecessary tooling from the final image, or document why they are retained. Removing unused packages would reduce the image’s attack surface and eliminate any vulnerabilities attributable to those packages, while reducing future vulnerability exposure and remediation effort.
  • Verify that any changes preserve backup, restore, and other supported operational functionality.

To Reproduce

  1. Run syft sbom analysis on the ghcr.io/cloudnative-pg/postgresql:17.10-system-trixie container image
    docker run --rm -v //var/run/docker.sock:/var/run/docker.sock anchore/syft:latest docker:ghcr.io/cloudnative-pg/postgresql:17.10-system-trixie --scope all-layers | Out-File -FilePath syft-sbom-postgresql-17.10-system-trixie.txt -Encoding utf8 -Force
  2. sbom report generation may take a few minutes, be patient
  3. Search for the mentioned packages in the sbom report
Lingua principale
HCL
Stelle
156
Fork
67
Merge medio
1g 15h
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di cloudnative-pg/postgres-containers

Tutte le issue di cloudnative-pg/postgres-containers

Issue simili

Altre issue su Databases

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.