[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Ben Faucher commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
I just ran into this issue. Is this going to be addressed? Why is the entrypoint overridden in the first place?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.178090.1485167605000.5205.1585833961010%40Atlassian.JIRA.
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nicolas De Loof assigned an issue to Unassigned
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
sachin gupta reopened an issue
I'm still facing the same issue with Jenkins version 2.161, I have search many issues opened and closed without any proper resolution to this problem, please provide the suitable resolution
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
sachin gupta
Resolution:
Fixed
Status:
Closed Reopened
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nicolas De Loof closed an issue as Fixed
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Nicolas De Loof
Status:
Resolved Closed
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nicolas De Loof commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Please don't re-open this issue, regression has been caught already and addressed in JENKINS-49278
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nicolas De Loof resolved as Fixed
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Nicolas De Loof
Status:
Reopened Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Nik Reiman commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Ditto here, 1.15 has caused a bunch of our container-related builds to fail. Looking at the diff of https://github.com/jenkinsci/docker-workflow-plugin/pull/116/files, it seems that the "detection" is looking for `cat` commands, which we are not using within `docker.image.inside`. Sadly the `–entrypoint ""` workaround also does not work in our case and we have reverted to 1.14 for now. Is there another JIRA issue already to track this regression, or should this one be re-opened?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Hans Kristian Flaatten commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
The 1.15 release really screwed up all of our builds involving containers. Reverted to 1.14.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Leo Luz edited a comment on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
We are using 1.15 in our company and we are having the same issue. My docker image has an entrypoint defined and {{image.inside()}} invokes docker as: {noformat} docker run -t -d -u 1000:1000 -w /var/jenkins/workspace/myimage:mytag cat {noformat} The problem is that {{cat}} is not a recognized flag for my entrypoint and it fails in the next command: {noformat} $ docker top 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 {noformat} with the error: {noformat} java.io.IOException: Failed to run top '52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4'. Error: Error response from daemon: Container 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 is not running at org.jenkinsci.plugins.docker.workflow.client.DockerClient.listProcess(DockerClient.java:140) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:185) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:19) {noformat} As a workaround Im doing in my Jenkinsfile: {noformat} script \ {↩image.inside('--entrypoint ""') \ {↩// do something}↩}↩ {noformat} This fixes my issue because I don't need the {{entrypoint}} definition at this stage but it would be nice to have the plugin working as expected. Thank you!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Leo Luz commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
We are using 1.15 in our company and we are having the same issue. My docker image has an entrypoint defined and image.inside() invokes docker as: docker run -t -d -u 1000:1000 -w /var/jenkins/workspace/myimage:mytag cat The problem is that cat is not a recognized flag for my entrypoint and it fails in the next command: $ docker top 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 with the error: java.io.IOException: Failed to run top '52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4'. Error: Error response from daemon: Container 52da7791facd2487ad299b815207b539f7c0f54ec0c53c66337b25f81a6c2bb4 is not running at org.jenkinsci.plugins.docker.workflow.client.DockerClient.listProcess(DockerClient.java:140) at org.jenkinsci.plugins.docker.workflow.WithContainerStep$Execution.start(WithContainerStep.java:185) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:19) As a workaround Im doing in my Jenkinsfile: script {↩ image.inside('--entrypoint ""') {↩ // do something }↩ }↩ This fixes my issue because I don't need the entrypoint definition at this stage but it would be nice to have the plugin working as expected. Thank you!
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Mike Kobit commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Any progress on this? Seems like this is related to https://issues.jenkins-ci.org/browse/JENKINS-38438 and https://issues.jenkins-ci.org/browse/JENKINS-39748 as well.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Jesse Glick updated JENKINS-41316
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Jesse Glick
Status:
In Review 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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Cyrille Le Clerc commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Andrew Bayer thanks!
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Andrew Bayer commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
I've put a PR up at https://github.com/jenkinsci/docker-workflow-plugin/pull/85 - it reverts .inside behavior to pre-JENKINS-37987 behavior, while adding a new .overrideEntrypoint method that works identically to how .inside worked post-JENKINS-37987.
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Andrew Bayer updated JENKINS-41316
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Andrew Bayer
Status:
In Progress Review
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title Andrew Bayer started work on JENKINS-41316 Change By: Andrew Bayer Status: Open In Progress 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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Andrew Bayer assigned an issue to Andrew Bayer
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Andrew Bayer
Assignee:
Andrew Bayer
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Cyrille Le Clerc commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
recampbell I took the flow of "Jenkins, The Definitive guide" and tried to make it work with as few differences as possible between:
A 'classic' linux build agent with Firefox that works with Java Selenium test frameworks
A vanilla linux build agent using docker-pipeline to customize the build environment and get the desired JDK, Maven & Firefox with Firefox working with Java Selenium test frameworks
A Docker based cloud agent (Kubernetes Agents, Amazon ECS Agents... ) so that the entire build runs in a Docker container that brings all the customization (JDK, Maven & Firefox)
Here is what I have succeeded to implement until docker-pipeline 1.8. The only trick was to switch the Selenium driver from Firefox to Remote+Firefox to use XVFB. The pipeline below is almost the same on classic linux, docker-pipeline and docker based cloud agents. Since docker-pipeline:1.8, I need to add something like "nohup /opt/bin/entry_point.sh &".
node ('docker'){
docker.image('cloudbees/java-build-tools:2.0.0').inside {
git 'https://github.com/cyrille-leclerc/game-of-life.git'
stage 'Build Web App'
withMaven(mavenSettingsConfig: 'maven-settings-for-gameoflife') {
sh "mvn clean package"
step([$class: 'ArtifactArchiver', artifacts: 'gameoflife-web/target/*.war'])
}
}
docker.image('cloudbees/java-build-tools:2.0.0').inside {
withMaven(
mavenSettingsConfig: 'maven-settings-for-gameoflife',
mavenLocalRepo: '.repository') {
sh """
cd gameoflife-acceptance-tests
mvn verify -Dwebdriver.driver=remote -Dwebdriver.remote.driver=firefox -Dwebdriver.remote.url="" class="code-comment" style="color: #808080">//localhost:/wd/hub -Dwebdriver.base.url=""
"""
}
}
}
Add Comment
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
recampbell commented on JENKINS-41316
Re: docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
It's not clear to me why your usecase is driving you to need docker.inside{}. When I use the selenium image, the withRun approach works great.
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-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Cyrille Le Clerc
The docker pipeline plugin used to honor the Dockerfile "entrypoint" until v1.8 in "{{docker.image('my-image').inside\{...\}}}". Since then, "entrypoint" is ignored.The capability to do selenium tests with a selenium-standalone-server running inside the Docker container fails since 1.8.This regression seems to be caused by JENKINS-37987 and the github commit " [\[FIXED JENKINS-37987\] Override ENTRYPOINT, not just command, for WithContainerStep|https://github.com/jenkinsci/docker-workflow-plugin/commit/5b0586d6bd87fc4f108693ee9361252a24eb37d1] ". This Jira seem to be similar to JENKINS-39748 h3. Testcaseh4. Code{code}node ("docker") {docker.image('cloudbees/java-build-tools:2.0.0').inside {// verify that selenium-standalone-server has been started by the Dockerfile entrypoint /opt/bin/entry_point.shsh "curl http://127.0.0.1:/wd/hub"// test with selenium pythonwriteFile (file: 'selenium_remote_web_driver_test.python', text: """#!/usr/bin/env python from selenium import webdriverfrom selenium.webdriver.common.desired_capabilities import DesiredCapabilitiesdriver = webdriver.Remote( command_executor='http://127.0.0.1:/wd/hub', desired_capabilities=DesiredCapabilities.FIREFOX)driver.get('http://python.org')assert 'Python' in driver.title""")sh "python selenium_remote_web_driver_test.python"}}{code}h4. ConsoleThe check "{{curl http://127.0.0.1:/wd/hub}}" will fail.{noformat}Started by user admin[Pipeline] nodeRunning on agent-1 in /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2[Pipeline] {[Pipeline] sh[testSelenium2] Running shell script+ docker inspect -f . cloudbees/java-build-tools:2.0.0.[Pipeline] withDockerContainer$ docker run -t -d -u 1000:1000 -w /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2 -v /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2:/home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2:rw -v /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2@tmp:/home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat cloudbees/java-build-tools:2.0.0[Pipeline] {[Pipeline] sh[testSelenium2] Running shell script+ curl http://127.0.0.1:/wd/hub % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 127.0.0.1 port : Connection refused[Pipeline] }$ docker stop --time=1
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Cyrille Le Clerc
The docker pipeline plugin used to honor the Dockerfile "entrypoint" until v1.8 in " {{docker.image('my-image').inside\{...\}}} " . Since then, "entrypoint" is ignored and the .The capability to do selenium tests with a selenium-standalone-server running inside the Docker container fails since 1 . 8. This regression seems to be caused by JENKINS-37987 and the github commit [\[FIXED JENKINS-37987\] Override ENTRYPOINT, not just command, for WithContainerStep|https://github.com/jenkinsci/docker-workflow-plugin/commit/5b0586d6bd87fc4f108693ee9361252a24eb37d1]This Jira seem to be similar to JENKINS-39748 h3. Testcaseh4. Code{code}node ("docker") {docker.image('cloudbees/java-build-tools:2.0.0').inside {// verify that selenium-standalone-server has been started by the Dockerfile entrypoint /opt/bin/entry_point.shsh "curl http://127.0.0.1:/wd/hub"// test with selenium pythonwriteFile (file: 'selenium_remote_web_driver_test.python', text: """#!/usr/bin/env python from selenium import webdriverfrom selenium.webdriver.common.desired_capabilities import DesiredCapabilitiesdriver = webdriver.Remote( command_executor='http://127.0.0.1:/wd/hub', desired_capabilities=DesiredCapabilities.FIREFOX)driver.get('http://python.org')assert 'Python' in driver.title""")sh "python selenium_remote_web_driver_test.python"}}{code}h4. ConsoleThe check "{{curl http://127.0.0.1:/wd/hub}}" will fail.{noformat}Started by user admin[Pipeline] nodeRunning on agent-1 in /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2[Pipeline] {[Pipeline] sh[testSelenium2] Running shell script+ docker inspect -f . cloudbees/java-build-tools:2.0.0.[Pipeline] withDockerContainer$ docker run -t -d -u 1000:1000 -w /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2 -v /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2:/home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2:rw -v /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2@tmp:/home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat cloudbees/java-build-tools:2.0.0[Pipeline] {[Pipeline] sh[testSelenium2] Running shell script+ curl http://127.0.0.1:/wd/hub % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 127.0.0.1 port : Connection refused[Pipeline] }$ docker stop
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Cyrille Le Clerc
The docker pipeline plugin used to honor the Dockerfile "entrypoint" until v1.8 in {{docker . image('my-image').inside\{...\}}}. Since then, "entrypoint" is ignored and the capability to do selenium tests fails.This regression seems to be caused by JENKINS-37987 and the github commit [\[FIXED JENKINS-37987\] Override ENTRYPOINT, not just command, for WithContainerStep|https://github.com/jenkinsci/docker-workflow-plugin/commit/5b0586d6bd87fc4f108693ee9361252a24eb37d1]This Jira seem to be similar to JENKINS-39748 h3. Testcaseh4. Code{code}node ("docker") {docker.image('cloudbees/java-build-tools:2.0.0').inside {// verify that selenium-standalone-server has been started by the Dockerfile entrypoint /opt/bin/entry_point.shsh "curl http://127.0.0.1:/wd/hub"// test with selenium pythonwriteFile (file: 'selenium_remote_web_driver_test.python', text: """#!/usr/bin/env python from selenium import webdriverfrom selenium.webdriver.common.desired_capabilities import DesiredCapabilitiesdriver = webdriver.Remote( command_executor='http://127.0.0.1:/wd/hub', desired_capabilities=DesiredCapabilities.FIREFOX)driver.get('http://python.org')assert 'Python' in driver.title""")sh "python selenium_remote_web_driver_test.python"}}{code}h4. ConsoleThe check "{{curl http://127.0.0.1:/wd/hub}}" will fail.{noformat}Started by user admin[Pipeline] nodeRunning on agent-1 in /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2[Pipeline] {[Pipeline] sh[testSelenium2] Running shell script+ docker inspect -f . cloudbees/java-build-tools:2.0.0.[Pipeline] withDockerContainer$ docker run -t -d -u 1000:1000 -w /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2 -v /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2:/home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2:rw -v /home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2@tmp:/home/ubuntu/jenkins-aws-home/workspace/tests/testSelenium2@tmp:rw -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e --entrypoint cat cloudbees/java-build-tools:2.0.0[Pipeline] {[Pipeline] sh[testSelenium2] Running shell script+ curl http://127.0.0.1:/wd/hub % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to 127.0.0.1 port : Connection refused[Pipeline] }$ docker stop --time=1 c65380bfd6c83d2290fc2e8fa8e5ae4cb0b84d1b21c66b4a3019c4a831f8833c$ docker rm -f
[JIRA] (JENKINS-41316) docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-41316
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
Change By:
Cyrille Le Clerc
Summary:
docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" no longer honored by docker-pipeline: since version 1.8
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.
