Just a friendly note to the community after talking it through with the support guys - slim-bookworm is having intermittent DNS resolver issues. We've narrowed one of our stack issues down to the actual image itself having issues and wanted to warn the community to save yourself a bit of aggravation. If you were debating moving everything to Alpine; let this be a final kick in that direction.
What's the worst that could happen?
My team recently encountered an issue with the Discovery Service where we received the following error in the console:
[Resolver Throttle] <ip here> has hit the max hit limit (250) and is being throttled.
After investigating, we discovered that our API was sending an excessive number of requests to a third-party service, which triggered the throttle in the Discovery Service. This throttling then impacted other API requests in our environment.
The Cycle team explained that the throttle is in place "to prevent getting banned from lookup services like Google's domain servers or other public nameservers." The throttle limit resets every five minutes.
We’ve since resolved the issue on our end, but I wanted to share this experience in case anyone else encounters a similar problem. Hopefully, this helps someone avoid the same situation.
I've never liked YAML ... probably for the same reason I've never liked python. Indent-sensitive configs? Gross.
... but I know so many of you love YAML. :(
We use cookies to enhance your experience. You can manage your preferences below.