Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

sregistry limit questions

See original GitHub issue

I have a local sregistry running, and have the following config items:

# grep LIMIT shub/settings/config.py 
USER_COLLECTION_LIMIT = 0
CONTAINER_WEEKLY_GET_LIMIT = 99999
COLLECTION_WEEKLY_GET_LIMIT = 99999
SREGISTRY_GOOGLE_BUILD_LIMIT = 9999
VIEW_RATE_LIMIT = "999999/1d"
VIEW_RATE_LIMIT_BLOCK = ( False )

However when things get busy, get the following error from “singularity push” operations:

FATAL:   Unable to push image to library: request did not succeed: http status code: 429

A simple loop will have me limited in about 20 push requests over the course of 15-30 minutes. Restarting the sregistry docker container resets the limits.

This is a private facing registry for an internal user group, and I don’t want to impose any limits on them at all. Is there a config item I’ve missed? I’ve attempted to set some of those values to “0” as well, with no luck (either the container won’t start, or the problem doesn’t go away).

Issue Analytics

State:
Created 3 years ago
Comments:7 (5 by maintainers)

Top GitHub Comments

1reaction

danmonscommented, Nov 1, 2020

Hi,

The settings didn’t take, but I haven’t had a chance to update the containers yet. I have a window to make that change tomorrow, so I’ll get back to you as soon as I’ve completed that.

0reactions

vsochcommented, Nov 1, 2020

Sounds good! We would want to check:

the version of ratelimit
confirm that you’ve restarted the containers

And we might need to look into if the ratelimit module uses a cache or some database model to determine rules - it could be that you make a change and then it’s not reflected because the database / cache still sees old requests.