-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Evergreen
-
None
-
Needed
-
Summary
Use pull through cache for DockerHub in Evergreen.
See https://docs.devprod.prod.corp.mongodb.com/devprod-platforms-ecr for steps.
Motivation
Who is the affected end user?
DBX devs testing in Evergreen.
How likely is it that this problem or use case will occur?
Likely. DEVPROD-12779 describes an earlier issue due to rate limiting.
If the problem does occur, what are the consequences and how severe are they?
Failing tests.
Is this issue urgent?
Quoting e-mail with subject "Announcement: Pull through cache for DockerHub is now available in Evergreen":
At the moment we have our Evergreen IPv6 range allow-listed by Docker, but they told us that it would go away eventually (no timeline on that, but we need to be ready).
Is this ticket only for tests?
Yes.
Acceptance Criteria
Use AWS ECR in Evergreen tasks pulling images from DockerHub.
- related to
-
DRIVERS-3158 Use AWS ECR pull through cache for DockerHub for Drivers Tools
-
- Backlog
-
- split to
-
NODE-6889 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
CDRIVER-5971 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
CSHARP-5556 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
CXX-3265 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
GODRIVER-3528 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
JAVA-5843 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
PYTHON-5267 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
RUBY-3642 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
RUST-2193 Use AWS ECR pull through cache for DockerHub
-
- Backlog
-
-
MOTOR-1450 Use AWS ECR pull through cache for DockerHub
-
- Closed
-
-
PHPLIB-1661 Use AWS ECR pull through cache for DockerHub
-
- Closed
-