Closed
Bug 1286279
Opened 8 years ago
Closed 6 years ago
Image builds failing with docker errors
Categories
(Taskcluster Graveyard :: Docker Images, defect)
Taskcluster Graveyard
Docker Images
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: dustin, Unassigned)
References
Details
per bug 1280178, https://treeherder.mozilla.org/#/jobs?repo=try&revision=a51a0a6aa227&selectedJob=23730813 + docker save try:fdb5ca86a0c117ec60d09217722ac193e34d5e5fb79574dd1646026b125087b4 time="2016-07-12T14:11:31Z" level=fatal msg="Get http:///var/run/docker.sock/v1.18/images/try:fdb5ca86a0c117ec60d09217722ac193e34d5e5fb79574dd1646026b125087b4/get: EOF. Are you trying to connect to a TLS-enabled daemon without TLS?" the job did eventually succeed, but that's a lot of retries..
Reporter | ||
Comment 1•8 years ago
|
||
We're seeing a similar thing now, and have been: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=3995b9f62fe34b2359addcac54ec9f68d79e5c3e Jonas, is this possibly an issue with the dind proxy?
Flags: needinfo?(jopsen)
Comment 3•8 years ago
|
||
Hmm, it could be.. It seems like the docker socket is EOF... Hmm, that could happen if perhaps the dind proxy is overloaded, say we are exporting a huge binary. Maybe it has to do with internal timeouts. This is all speculation, we should probably find a more reliable solution than the dind proxy thing.
Flags: needinfo?(jopsen)
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Taskcluster → Taskcluster Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•