[JIRA] (JENKINS-42322) Docker rm/stop/... commands killed by the timeout, failing builds

82 views
Skip to first unread message

david.parsson@gmail.com (JIRA)

unread,
Mar 30, 2017, 3:42:03 AM3/30/17
to jenkinsc...@googlegroups.com
David Pärsson updated an issue
 
Jenkins / Bug JENKINS-42322
Docker rm/stop/... commands killed by the timeout, failing builds
Change By: David Pärsson
Summary: Fail to Docker rm a container started with inside {} /stop/... commands killed by the timeout, failing builds
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

kyu@fortinet.com (JIRA)

unread,
Mar 30, 2017, 2:45:01 PM3/30/17
to jenkinsc...@googlegroups.com
Kevin Yu commented on Bug JENKINS-42322
 
Re: Docker rm/stop/... commands killed by the timeout, failing builds

Basically i'm seeing the exact same symptom as described by Yuriy. Downgraded to 1.9.1 and so far I've not seen this issue

gustavo@gnustavo.com (JIRA)

unread,
Jun 17, 2018, 4:33:03 PM6/17/18
to jenkinsc...@googlegroups.com

I'm commenting to report that we begun facing similar errors last week, after we changed several pipeline scripts, which increased the frequency with which we launch Docker containers.

We're using Jenkins 2.107.2 and docker-workflow-plugin 1.17.

I increased the plugin timeout to 250s and decreased the number of executors in our slaves to no avail.

In despair, I patched the plugin to make it ignore docker-rm errors. Using the patched plugin we were able to finish all of our weekend builds successfully.

I know this is not a decent solution. I feared that our builds could be delayed waiting for the stuck containers, but I didn't notice this or any other side effect. So, for now, we'll use this patched plugin.

I don't understand yet what makes the docker-rm command delay. Do you have some hints to share?

svanoort@cloudbees.com (JIRA)

unread,
Oct 31, 2018, 12:20:03 PM10/31/18
to jenkinsc...@googlegroups.com

Gustavo Chaves Which version of Docker itself are you using, and do you see the timeout error, or just the error "Failed to rm container" ?

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

chrismaes87@gmail.com (JIRA)

unread,
Mar 25, 2020, 8:27:03 AM3/25/20
to jenkinsc...@googlegroups.com

Jesse Glick: thanks for the hint, this seems to help. We now have one timeout with 280 seconds... You say around 300 and more will probably not work. Has this been verified? What kind of error or so would you expect if we put a value above 300?

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages