Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Review unnecessary Python packaging tools in PostgreSQL image

Abierto
  • ¿Algo no está bien?
#524 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@benispeti ya está trabajando en esto.

Desde el 11/10/2026.

  • #527 de @benispeti — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, postgresql, python
Área
databases, infrastructure

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
HCL
Estrellas
156
Forks
67
Merge medio
1 d 15 h
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cloudnative-pg/postgres-containers

Todos los issues de cloudnative-pg/postgres-containers

Issues similares

Más issues de Databases

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.