Connecting to Ryuk failed

[nikolayk812]

Describe the bug
Sometimes I get this:
failed to create container: connecting to reaper failed: Connecting to Ryuk on localhost:32787 failed: dial tcp [::1]:32787: connect: connection refused

Then I restart the test and then it works.

To Reproduce
Not known to me

Expected behavior
No such error

** docker info **
output of the command:

Client:
 Debug Mode: false

Server:
 Containers: 28
  Running: 0
  Paused: 0
  Stopped: 28
 Images: 116
 Server Version: 19.03.5
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: b34a5c8af56e510852c35414db4c1f4fa6172339
 runc version: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.76-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 1.943GiB
 Name: docker-desktop
 ID: BXSA:MCZH:LQVP:DID3:JENA:NDE4:NWOL:D355:BAQV:COEX:HNY4:QNC5
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 35
  Goroutines: 52
  System Time: 2020-02-10T21:20:41.4269363Z
  EventsListeners: 3
 HTTP Proxy: gateway.docker.internal:3128
 HTTPS Proxy: gateway.docker.internal:3129
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

[itaischwartz]

Happened to me too

[gianarb]

Hello! I don't remember if there is a retry logic around it, if it is missed, we should add one. Thanks for reporting this!

…

On Wed, Feb 12, 2020 at 9:57 AM Itai Schwartz ***@***.***> wrote: Happened to me too — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#149?email_source=notifications&email_token=AAMOAO5GMATCEX4EHHL6KITRCO2ZFA5CNFSM4KSV2MF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELP6XQQ#issuecomment-585100226>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMOAO5SK4GH6CRCIDVZHVLRCO2ZFANCNFSM4KSV2MFQ> .

-- Gianluca Arbezzano www.gianarb.it

[mdonkers]

For whoever finds this issue (like me). There might be another reason to get the above error. I created a new ticket:
#764

(tests that don't use a container might cause the Ryuk reaper container to time-out and shutdown, after which it cannot be re-used again for subsequent tests)