Testcontainers-java: A connection to http://docker.socket/ was leaked

[vmassol]

Hi guys, just noticed that the following warning happens from time to time (not easy to reproduce):

12:08:27.540 [main] INFO  o.x.t.d.i.j.XWikiDockerExtension - (*) Start VNC container...
12:08:32.120 [main] INFO  o.x.t.d.i.j.XWikiDockerExtension - (*) Starting test [deleteChildren]
Dec 22, 2019 12:08:52 PM org.testcontainers.shaded.okhttp3.internal.platform.Platform log
WARNING: A connection to http://docker.socket/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
12:08:52.845 [main] INFO  o.x.t.d.i.j.XWikiDockerExtension - (*) Stopping test [deleteChildren]

Anything that can be done?

I'll try to reproduce with the log level set to FINE.

[bsideup]

Hi @vmassol,

Thanks for the report!
There was an issue in docker-java that caused some InputStreams to leak:
https://github.com/docker-java/docker-java/pull/1290

We're working on releasing docker-java 3.2.0 (that includes the fix) and will upgrade it in Testcontainers shortly after.

[vmassol]

Excellent! Thanks

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[vmassol]

I guess this should stay open... Unless the last version of TC (1.13.0) includes docker-java 3.2.0 already?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this is a mistake, please reply to this comment to keep it open. If there isn't one already, a PR to fix or at least reproduce the problem in a test case will always help us get back on track to tackle this.

[rnorth]

@bsideup is actively working on this - not stale!

[stale[bot]]

This issue has been automatically closed due to inactivity. We apologise if this is still an active problem for you, and would ask you to re-open the issue if this is the case.

[nachevn]

@bsideup any updates here?

Thanks
Nikolay

[bsideup]

@nachevn good question! Any updates? Is it still reproducible with the latest Testcontainers that depends on docker-java 3.2.x? :)

[nachevn]

@bsideup yes, indeed it is a good question. It occurs but not every time which makes it (unfortunately) not reproducible. Just for information we are using testcontainers version 1.15.0-rc1

[ravenblackdusk]

@bsideup I'm getting this on 1.15.0

[bsideup]

@ravenblackdusk please try 1.15.1 then :)

[ravenblackdusk]

@bsideup I'm still getting this with 1.15.1

[perlun]

@bsideup Regretfully also seeing this on 1.15.1 sometimes.