[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title Joao Simas commented on JENKINS-55066 Re: Docker plugin erroneously terminates containers shortly after they start I'm having exactly the same behavior. Did you found any solution? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196118.1544159082000.2646.1564397940121%40Atlassian.JIRA.
[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title Ali Narenji commented on JENKINS-55066 Re: Docker plugin erroneously terminates containers shortly after they start Is there any workaround on the issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196118.1544159082000.24783.1560229740121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-55066 Docker plugin erroneously terminates containers shortly after they start Change By: Nicolas De Loof Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title
Owen Mehegan updated an issue
Jenkins / JENKINS-55066
Docker plugin erroneously terminates containers shortly after they start
Change By:
Owen Mehegan
We are seeing an issue where Pipeline jobs using Docker agents (with the Docker plugin, as opposed to Docker containers on regular agents using Pipeline's Docker support) intermittently fail right at the start, during the initial git checkout, with a "FATAL: java.io.IOException: Unexpected termination of the channel" exception. Having enabled debug logging for the Docker plugin, it appears that the plugin is erroneously killing the container because it thinks it is no longer needed.Job log:{noformat}[First few lines redacted, this is the Jenkinsfile checkout]Checking out Revision 0b45f687992585a470e5faf003309b215e3f74f1 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0b45f687992585a470e5faf003309b215e3f74f1FATAL: java.io.IOException: Unexpected termination of the channeljava.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2679)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3154)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)at java.io.ObjectInputStream.(ObjectInputStream.java:358)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)at hudson.remoting.Command.readFrom(Command.java:140)at hudson.remoting.Command.readFrom(Command.java:126)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-2ae12755b75761at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)at hudson.remoting.Request.call(Request.java:202)at hudson.remoting.Channel.call(Channel.java:954)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)at com.sun.proxy.$Proxy118.withRepository(Unknown Source)at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title
Owen Mehegan updated an issue
Jenkins / JENKINS-55066
Docker plugin erroneously terminates containers shortly after they start
Change By:
Owen Mehegan
We are seeing an issue where Pipeline jobs using Docker agents (with the Docker plugin, as opposed to Docker containers on regular agents using Pipeline's Docker support) intermittently fail right at the start, during the initial git checkout, with a "FATAL: java.io.IOException: Unexpected termination of the channel" exception. Having enabled debug logging for the Docker plugin, it appears that the plugin is erroneously killing the container because it thinks it is no longer needed.Job log:{noformat}[First few lines redacted, this is the Jenkinsfile checkout]Checking out Revision 0b45f687992585a470e5faf003309b215e3f74f1 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0b45f687992585a470e5faf003309b215e3f74f1FATAL: java.io.IOException: Unexpected termination of the channeljava.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2679)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3154)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)at java.io.ObjectInputStream.(ObjectInputStream.java:358)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)at hudson.remoting.Command.readFrom(Command.java:140)at hudson.remoting.Command.readFrom(Command.java:126)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-2ae12755b75761at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)at hudson.remoting.Request.call(Request.java:202)at hudson.remoting.Channel.call(Channel.java:954)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)at com.sun.proxy.$Proxy118.withRepository(Unknown Source)at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271)at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244)at hudson.scm.SCM.checkout(SCM.java:504)at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-55066 Docker plugin erroneously terminates containers shortly after they start Issue Type: Bug Assignee: Nicolas De Loof Components: docker-plugin Created: 2018-12-07 05:04 Priority: Major Reporter: Owen Mehegan We are seeing an issue where Pipeline jobs using Docker agents (with the Docker plugin, as opposed to Docker containers on regular agents using Pipeline's Docker support) intermittently fail right at the start, during the initial git checkout, with a "FATAL: java.io.IOException: Unexpected termination of the channel" exception. Having enabled debug logging for the Docker plugin, it appears that the plugin is erroneously killing the container because it thinks it is no longer needed. Job log: [First few lines redacted, this is the Jenkinsfile checkout] Checking out Revision 0b45f687992585a470e5faf003309b215e3f74f1 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0b45f687992585a470e5faf003309b215e3f74f1 FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2679) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3154) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at
