Skip to content

Historical APK inputs for postgres:17.10-alpine3.24 amd64 build ID 4348d3fff6140abf13d20ac4712684c1fbe29f2e2f74f1c32627fa80859ede0f #1429

Open

Description

@SpiritTrapper

Hello, we are verifying the exact published PostgreSQL 17.10 Alpine 3.24 amd64 image and need the historical Alpine package inputs used by its July 7, 2026 build. The selected published amd64 manifest is sha256:af194ccf3e2d7fe367012c7b88ce8b816c5c889b18a5b316799a1f0d7eac746a. The image's provenance identifies Jenkins build ID 4348d3fff6140abf13d20ac4712684c1fbe29f2e2f74f1c32627fa80859ede0f and BuildKit invocation 3f3hheq4ybxofix642tfwazj6; the docker-library/meta historical builds.json maps this build to staging index sha256:331cc2bd1fdb9c12b831cc539ab472d91f7cdc99a2fb755b76832a50047ed7d8.

Could you provide a retrievable, verifiable archive or exact immutable links for:

  1. The signed Alpine v3.24 main and community x86_64 APKINDEX bytes used by that build, with signatures and repository URLs.
  2. The exact .apk payload bytes or immutable content digests for packages fetched at build time, including transient build dependencies, plus their signature verification chain.
  3. Any retained builder cache, build logs or attestation that binds those inputs to this Jenkins build ID / BuildKit invocation.

If the publisher does not retain these artifacts, please confirm that and identify the authoritative Alpine archive or build records that could establish the exact inputs. Current rolling APKINDEX files do not contain all historical package versions observed in the published image, so they cannot serve as replacements. We are asking for provenance evidence only; no image rebuild or security conclusion is requested.

Public provenance references:

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions