How to see the API ratelimit of the github packages docker registry

[jonas-zipprick]

Select Topic Area

Question

Body

When trying to push private docker image to ghcr.io we often times see this error:

error parsing HTTP 429 response body: unexpected end of JSON input: ""

The error is printed by the docker client.
I assume we are pushing images to fast. But where/how can I see the rate limit and how much of the quota is used?
The billing section in the organisation settings doesn't show me anything.

[jge162]

@jonas-zipprick GitHub Package Registry (GHCR) rate limits are based on your GitHub account's current plan. You can check your current rate limit by sending a GET request to the following API endpoint: https://api.github.com/rate_limit.

If you're hitting rate limits, you can try the following:

Wait a while and try again later.
Use a token with fewer permissions.
Upgrade your GitHub account plan.

[jonas-zipprick]

Thanks jge162.
Unfortunately, your answer did not help me.

I executed
curl -u balugege:xxxx https://api.github.com/rate_limit
on our CI worker.
"balugege" is my old username.
I pulled the credentials from ~/.docker/config.json

This was the response:

{
  "resources": {
    "core": {
      "limit": 5000,
      "used": 0,
      "remaining": 5000,
      "reset": 1674640520
    },
    "search": {
      "limit": 30,
      "used": 0,
      "remaining": 30,
      "reset": 1674636980
    },
    "graphql": {
      "limit": 5000,
      "used": 5,
      "remaining": 4995,
      "reset": 1674640258
    },
    "integration_manifest": {
      "limit": 5000,
      "used": 0,
      "remaining": 5000,
      "reset": 1674640520
    },
    "source_import": {
      "limit": 100,
      "used": 0,
      "remaining": 100,
      "reset": 1674636980
    },
    "code_scanning_upload": {
      "limit": 1000,
      "used": 0,
      "remaining": 1000,
      "reset": 1674640520
    },
    "actions_runner_registration": {
      "limit": 10000,
      "used": 0,
      "remaining": 10000,
      "reset": 1674640520
    },
    "scim": {
      "limit": 15000,
      "used": 0,
      "remaining": 15000,
      "reset": 1674640520
    },
    "dependency_snapshots": {
      "limit": 100,
      "used": 0,
      "remaining": 100,
      "reset": 1674636980
    }
  },
  "rate": {
    "limit": 5000,
    "used": 0,
    "remaining": 5000,
    "reset": 1674640520
  }
}

The usage report for our organisation shows no usage at all:

We are currently on a team plan.
How many docker push can we execute per hour?
How many packages would we be able to push with the enterprise plan?

The token we use has permissions: delete:packages, repo, workflow, write:packages

[jge162]

no usage at all. huh

[aflansburg]

We have begun seeing this identical error sparsely at random intervals on CircleCI when pushing to GHCR as well. Requests are authenticated we confirm that we have not hit a rate limit. Also, per the Github docs, they return 403 and not 429, so it does not appear to be associated with the typical API limits. The only thing I can think of is how docker push works under the hood - namely, that it pushes 5 layers of an image at a time. It's possible that our CI is doing something inexplicably funky here (which wouldn't be abnormal for Circle configs) causing the issue.

Good docs on rate limits here -> https://docs.github.com/en/rest/overview/resources-in-the-rest-api?apiVersion=2022-11-28#checking-your-rate-limit-status

[ernst77]

Having the same issue, none of the rate limits being used

but cannot upload image to registry

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬