publish roboflow/roboflow-inference-server-cpu to AWS ECR in addition to Dockerhub
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 319
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 133
Description
Search before asking
- I have searched the Inference issues and found no similar feature requests.
Description
I'm trying to deploy roboflow/roboflow-inference-server-cpu via ECS Fargate on AWS. Because I am not a Dockerhub customer, I am experiencing rate limits from a low number of image pulls per hour.
If you publish roboflow/roboflow-inference-server-cpu to the public AWS ECR gallery, I will not be subject to the rate limits.
As a workaround, I am manually publishing roboflow/roboflow-inference-server-cpu to a private ECR repository.
Use case
This will allow teams to pull your docker images from AWS ECR and not be subject to Dockerhub rate limits.
Additional
No response
Are you willing to submit a PR?
- Yes I'd like to help by submitting a PR!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how roboflow/roboflow-inference-server-cpu is currently published to Docker Hub and the repository's deployment or release automation. Then check the requirements for publishing the image to the public AWS ECR gallery. Done means the image is available there and the publication process is documented or automated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, docker
- Domain
- cloud, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100