Closed Bug 1156326 Opened 10 years ago Closed 9 years ago

[garndt-q2-goal] Investigate/implement pushing/pulling docker images to s3

Categories

(Taskcluster :: General, defect)

Product:
Taskcluster
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: garndt, Unassigned)

References

Details

To reduce the dependencies on quay/docker hub, and to increase availablity/speed, look into implementing some kind of registry like s3 backed store for images. Images could be squashed and then the tarball stored on s3.
Depends on: 1162377
So there were some initial investigations related
Depends on: 1170999
Now that 1170999 (docker image pull retry) has been landed, I have not been seeing any task aborts related to images not being pulled. That and in combination with moving to docker hub has made the immediate necessity of moving to a private registry unnecessary, at least in the very near term future.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: TaskCluster → General
Product: Testing → Taskcluster
Target Milestone: --- → mozilla41
Version: unspecified → Trunk
Resetting Version and Target Milestone that accidentally got changed...
Target Milestone: mozilla41 → ---
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.