Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Add container repository content-consistency preflight validation

オープン
  • 何か問題がありますか？
#2,473 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
docker
領域
backend

調査の方向性

Start by tracing the repository-version publication path and the existing handling of image manifests, configuration blobs, layers, and multi-platform indexes. Define validation against one immutable repository version, then add coverage for complete and incomplete graphs, aggregated errors, non-modification, and large referenced-blob sets with bounded memory use.

索引モデルが issue の本文から書いたものです。

説明

Problem

Container images form a content graph: manifests reference configuration and layer blobs, while manifest lists/image indexes reference platform-specific manifests.

When repository content is synchronized, uploaded, copied, or assembled into a repository version, inconsistencies in this graph may not become visible until a client attempts to pull the affected image.

It would be useful for Pulp Container to provide a container-specific preflight validation that detects incomplete or inconsistent image content before it is published.

Proposed solution

Add an optional validation step that checks the integrity of container content before publication.

The validation should identify:

  • manifests referencing missing blobs
  • image indexes referencing missing manifests
  • manifests whose referenced configuration is unavailable
  • incomplete multi-platform image indexes
  • references to content that is not present in the repository version being published

Instead of returning only the first failure, the validation should collect the affected image references and missing content so an administrator can correct the repository in a single operation.

Example:

Container repository validation failed

image: example/app:latest

Missing:
  sha256:abc... (config)
  sha256:def... (layer)

image: example/app:arm64

Missing:
  sha256:123... (manifest)

Requirements

  • Validation must operate against a specific immutable repository version.
  • Validation must not modify repository content.
  • Validation should avoid repeatedly querying the same content objects.
  • The operation should provide actionable errors suitable for both API clients and task logs.
  • Validation should support multi-platform image indexes.
  • Large repositories should be handled without loading the complete content graph into memory.

Acceptance criteria

  • A repository version containing a complete image graph passes validation.
  • Missing manifests are detected.
  • Missing configuration blobs are detected.
  • Missing layer blobs are detected.
  • Broken image-index references are detected.
  • Multiple inconsistencies are reported together.
  • Validation does not modify repository content.
  • Tests cover single-platform images and multi-platform indexes.
  • Tests cover large numbers of referenced blobs without excessive memory usage.

Motivation

Pulp Container is responsible for distributing OCI/Docker container content. Detecting an inconsistent content graph before publication would move failures from the consumer side of the registry to the repository-management side, where they can be diagnosed and corrected before users attempt to pull the affected images.

主要言語
Python
スター
31
フォーク
57
平均マージ
1日 8時間
マージ済み PR（30日）
87

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

pulp/pulp_container のほかの issue

pulp/pulp_container の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。