Question
ERROR: failed to access run image: connect to repo store 'digitaloceanapps/apps-run:7858f2c'
- Posted on June 20, 2022
- DigitalOcean App PlatformDjango
Asked by Rexford Nkansah
As the title says, that’s the error I get, trying to deploy a Django application onto App Platform
[backend] [2022-06-20 14:01:17] ERROR: failed to access run image: connect to repo store ‘digitaloceanapps/apps-run:7858f2c’: GET https://index.docker.io/v2/digitaloceanapps/apps-run/manifests/7858f2c: TOOMANYREQUESTS: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
Is it something I need to do? I’ve checked my insights, and there’s no network traffic. It’s a demo app nobody even has access to, so it doing too many requests is even weird to begin with.
The django project has two components, one as a web service (Python) and one as a Static Site for serving the assets.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Hey @seanmavley,
I believe this is a known issue affecting a few builds on App Platform currently that the team are looking into.
I’ve run into this myself before during a build and got around it by retrying the build/deployment again :)
Let me know how that goes for you. - Matt.