[JIRA] (JENKINS-40168) Make the override of ENTRYPOINT by image.inside optional

2017-01-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40168  
 
 
  Make the override of ENTRYPOINT by image.inside optional   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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-40168) Make the override of ENTRYPOINT by image.inside optional

2016-12-01 Thread ethan.trewh...@gtri.gatech.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ethan Trewhitt created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40168  
 
 
  Make the override of ENTRYPOINT by image.inside optional   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2016/Dec/01 9:22 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Ethan Trewhitt  
 

  
 
 
 
 

 
 The change made to address JENKINS-37987 breaks Docker images that use a specific ENTRYPOINT to start services. Any Docker image based on the common scenario of using supervisord to run a set of daemons will break with the override of ENTRYPOINT and CMD by image.inside, which overrides the command to "cat" to keep the image alive. While some users may need that behavior, many of us would prefer to control that directly.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment