With a large projects repository withh hundreds of simulateanous builds we encountered several times builds lost , impossible to stop or restart withoutt any kind of message in the logs.... Default docker-java implementation uses Netty  as a communication layer  and Netty handling for timeouts requires tricky code.....

      So I tried to drop the default transport mode to use Apache HC5 instead . The results (in production) are quite good and we do not loose builds anymore.

      But our code is not conformant to quality level as expectedby the Jenkins devs & users. 

          [JENKINS-65872] Jobs lost while using docker plugin

          jerome moliere created issue -
          pjdarton made changes -
          Link New: This issue duplicates JENKINS-66025 [ JENKINS-66025 ]
          pjdarton made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            jmoliere jerome moliere
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: