[
https://issues.apache.org/jira/browse/BEAM-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654199#comment-16654199
]
Scott Wegner commented on BEAM-5783:
------------------------------------
A quick search around the internet seems to indicate this is a random Docker
flake. [This GitHub
issue|https://github.com/moby/moby/issues/31849#issuecomment-320236354] looks
similar. It was closed because it couldn't be reproduced:
bq. Unfortunately, the docker: Error response from daemon: grpc: the connection
is unavailable. error is quite generic. Basically it means: the docker daemon
(dockerd) was unable to make a gRPC connection with the containerd daemon
(docker-containerd); in one of the cases above, this was due to a kernel panic,
but other situations, such as the system OOM-killing the daemon could have the
same result.
> [beam_PreCommit_Website_Commit] [buildDockerImage] grpc: the connection is
> unavailable
> --------------------------------------------------------------------------------------
>
> Key: BEAM-5783
> URL: https://issues.apache.org/jira/browse/BEAM-5783
> Project: Beam
> Issue Type: Bug
> Components: test-failures, website
> Reporter: Scott Wegner
> Assignee: Melissa Pashniak
> Priority: Major
> Labels: currently-failing
>
> _Use this form to file an issue for test failure:_
> * [Jenkins
> Job|https://builds.apache.org/job/beam_PreCommit_Website_Commit/339/]
> * [Gradle Build
> Scan|https://scans.gradle.com/s/f66kbflbvgbhs/console-log?task=:beam-website:buildDockerImage#L11]
> * [Test source
> code|https://github.com/apache/beam/blob/45612dff7539ec8d026f13d80e233ae9086f46b6/website/Dockerfile#L25]
> Initial investigation:
> The failure occurred running {{gem install bundler}} during the Docker
> container build:
> {{grpc: the connection is unavailable}}
> ----
> _After you've filled out the above details, please [assign the issue to an
> individual|https://beam.apache.org/contribute/postcommits-guides/index.html#find_specialist].
> Assignee should [treat test failures as
> high-priority|https://beam.apache.org/contribute/postcommits-policies/#assigned-failing-test],
> helping to fix the issue or find a more appropriate owner. See [Apache Beam
> Post-Commit
> Policies|https://beam.apache.org/contribute/postcommits-policies]._
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
