Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Pull-through from gcr.io returns 500 when pulling using podman/buildah

Closed Beginner friendly
#2,581 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #2582 by @am9zZWY — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start by locating RegistryauthHttpDownloader.update_token() and tracing how it parses the www-authenticate header shown in the report. Reproduce the pull-through request with gcr.io using podman or buildah, then verify authentication handles the unquoted service value and the pull succeeds without a 500 response.

Written by the indexing model from the issue text.

Description

Issue Triage-Needed

Version
pulp core: 3.121.1
pulp container: 2.30.0.dev

Describe the bug
Pulling from gcr.io through Pulp using podman/buildah/... (not docker) triggers a 500 error. The problem is that GCR returns unquoted headers which RegistryauthHttpDownloader.update_token() cannot parse.
These are the auth headers: www-authenticate: Bearer realm="https://gcr.io/v2/token",service=gcr.io

This is the error message:

pulp [649060ba005445eb899bebabe59c29d7]: django.request:ERROR: Internal Server Error: /extensions/v2/gcr/distroless/static/signatures/sha256:2293b36c7c9082bf4115aab724b4d2cddec82c8eba39bf27ac0517e159acf150"

To Reproduce
Setup a pull-through distribution with gcr.io as remote and pull through Pulp using podman/buildah/...

Expected behavior
Handle authentication headers correctly

Dominant language
Python
Stars
31
Forks
57
Avg merge
21h 31m
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pulp/pulp_container

All issues in pulp/pulp_container

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.