Fix: Second execution of a docker command in Netty implementation always fails by tejksat · Pull Request #630 · docker-java/docker-java
Unable to setup a valuable integration test because TestDockerCmdExecFactory changes default DockerCmdExecFactoryImpl behavior in the way it becomes pointless. It creates WebTarget on every exec() invocation:
"main@1" prio=5 tid=0x1 nid=NA runnable
java.lang.Thread.State: RUNNABLE
at com.github.dockerjava.netty.WebTarget.<init>(WebTarget.java:28)
at com.github.dockerjava.netty.DockerCmdExecFactoryImpl.getBaseResource(DockerCmdExecFactoryImpl.java:577)
at com.github.dockerjava.netty.DockerCmdExecFactoryImpl.createCreateContainerCmdExec(DockerCmdExecFactoryImpl.java:396)
at com.github.dockerjava.core.TestDockerCmdExecFactory$1.exec(TestDockerCmdExecFactory.java:103)
at com.github.dockerjava.core.TestDockerCmdExecFactory$1.exec(TestDockerCmdExecFactory.java:100)
at com.github.dockerjava.core.command.AbstrDockerCmd.exec(AbstrDockerCmd.java:35)
at com.github.dockerjava.core.command.CreateContainerCmdImpl.exec(CreateContainerCmdImpl.java:177)
...