Closed
Bug 1182490
Opened 9 years ago
Closed 9 years ago
[garndt-q3/2015-goal] Investigate and implement docker images as artifacts
Categories
(Taskcluster :: Workers, defect)
Taskcluster
Workers
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: garndt, Assigned: garndt)
References
Details
If possible implement a solution that would allow docker images to be loaded from artifacts created by other tasks. Most of the discussion has been documented in this etherpad: https://etherpad.mozilla.org/jonasfj-docker-build-images
Updated•9 years ago
|
Component: TaskCluster → General
Product: Testing → Taskcluster
Assignee | ||
Updated•9 years ago
|
Component: General → Docker-Worker
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → garndt
Comment 1•9 years ago
|
||
For the benefit of sheriffs: please note this means we can avoid hitting docker registries at all, since we would pull down artifacts from s3, and use `docker load` to mount them. Currently we use `docker pull` which hits a docker registry, and uses the registry to return the artifacts. A lot of problems we had with docker images until now were related to unreliable docker registry services from quay/dockerhub. This bug removes the dependency, so we are only then depending on s3 directly for blob storage.
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: Docker-Worker → Workers
You need to log in
before you can comment on or make changes to this bug.
Description
•