Closed
Bug 1320776
Opened 8 years ago
Closed 8 years ago
image_builder fails
Categories
(Taskcluster Graveyard :: Docker Images, defect)
Taskcluster Graveyard
Docker Images
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jonasfj, Assigned: jonasfj)
References
Details
Example:
https://tools.taskcluster.net/task-inspector/#eJdJazH9TMCE6TCAKbPh-A/
Probably curl is timing out, or maybe the default speed-limit is killing curl.
TODO: Review https://curl.haxx.se/docs/manpage.html for things that could break a long lived slow http connection to a unix socket.
Assignee | ||
Comment 1•8 years ago
|
||
Playing with CURL looks like it could be node in dind-service that timeouts.
We might just have to do: res.socket.setTimeout(20 min), and then it should be fine.
Assignee | ||
Comment 2•8 years ago
|
||
just landed: https://github.com/taskcluster/dind-service/pull/4
And deployed on taskcluster-images.
I tested an image build, so hopefully this removes the intermittence.
Please let me know if it doesn't.
Note: This removed some internal timeout in our docker proxy service.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Taskcluster → Taskcluster Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•