[JIRA] (JENKINS-57136) Allow users to customize docker timeouts

[dlrms...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keunhong Lee updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57136  
 
 
  Allow users to customize docker timeouts   
 

  
 
 
 
 

 
Change By: 
 Keunhong Lee  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 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-57136) Allow users to customize docker timeouts

[dlrms...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Keunhong Lee created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57136  
 
 
  Allow users to customize docker timeouts   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin, pipeline  
 
 
Created: 
 2019-04-22 08:04  
 
 
Environment: 
 Jenkins installed directly to a Debian LXC and docker is installed inside the LXC.  Jenkins runs outside the docker but the user 'jenkins' has 'docker' group access.   
 
 
Labels: 
 configuration pipeline  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Keunhong Lee  
 

  
 
 
 
 

 
 Though docker enables fast creation of containers, docker is still slow when being executed under legacy environment (e.g. dir file system). Though the timeout for docker commands has been increased to 180/300 seconds by https://issues.jenkins-ci.org/browse/JENKINS-42322, I think the timeout should be configurable.   I sometimes get failure like this: 

 

ERROR: Timeout after 180 seconds
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

java.io.IOException: Failed to run image ''. Error:
 

 However, the same code just succeeded its build few minutes ago. That's because the execution time of a docker command varies depending on the system load. In my example, it