[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau created an issue

Jenkins / JENKINS-51307 Declarative pipeline and docker entrypoint Issue Type: New Feature Assignee: vjuranek Components: docker-build-step-plugin Created: 2018-05-14 18:11 Environment: problem occurs on version 1.15 and above of the plugin Priority: Major Reporter: Frederic Rousseau I write a dead simple Dockerfile   FROM openjdk:8-jdk-alpine ENTRYPOINT "java"   I write a dead simple declarative pipeline pipeline {     agent { dockerfile true }     stages {         stage('Dead Simple') {             steps {                 checkout scm             }         }     } } I get an error. I get the same error with  pipeline {     agent { docker 'openjdk:8-jdk-alpine' }     stages {         stage('Dead Simple') {             steps {                 checkout scm             }         }     } } The error is ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`. I cannot pass --entrypoint to the run command, it's jenkins that call it a bit more logs : [Pipeline] withDockerContainer Jenkins does not seem to be running inside a container $ docker run -t -d -u 107:111 -w /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:rw,z -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** 4d6ffe9d9713df374dd2670073b9ea32598df407 cat $ docker top 13d063e7996ad4476075baf7586aa3186d0bff08cdbd4c10205327bb6b44c75b -eo pid,comm ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau updated an issue

Jenkins / JENKINS-51307 Declarative pipeline and docker entrypoint

Change By: Frederic Rousseau

I write a dead simple Dockerfile

{code:java}

FROM openjdk:8-jdk-alpine ENTRYPOINT "java"

{code}

I write a dead simple declarative pipeline

{code:java}

pipeline {     agent { dockerfile true }     stages {         stage('Dead Simple') {             steps {                 checkout scm             }         }     }

}{code}

I get an error. I get the same error with

{code:java}

pipeline {     agent { docker 'openjdk:8-jdk-alpine' }     stages {         stage('Dead Simple') {             steps {                 checkout scm             }         }     }

}{code} The error is {code:java}

ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.

{code} I cannot pass --entrypoint to the run command, it's jenkins that call calls it a bit more logs : {code:java}

[Pipeline] withDockerContainer Jenkins does not seem to be running inside a container $ docker run -t -d -u 107:111 -w /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:rw,z -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** 4d6ffe9d9713df374dd2670073b9ea32598df407 cat $ docker top 13d063e7996ad4476075baf7586aa3186d0bff08cdbd4c10205327bb6b44c75b -eo pid,comm ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`.

{code}

Add Comment

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau updated an issue

Jenkins / JENKINS-51307

Declarative pipeline and docker entrypoint

Change By: Frederic Rousseau Issue Type: New Feature Bug

Add Comment

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau updated an issue

Jenkins / JENKINS-51307 Declarative pipeline and docker entrypoint Change By: Frederic Rousseau

I cannot pass --entrypoint to the run command, it's jenkins that calls it

a bit more logs : {code:java} [Pipeline] withDockerContainer Jenkins does not seem to be running inside a container $ docker run -t -d -u 107:111 -w /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:rw,z -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** 4d6ffe9d9713df374dd2670073b9ea32598df407 cat $ docker top 13d063e7996ad4476075baf7586aa3186d0bff08cdbd4c10205327bb6b44c75b -eo pid,comm ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`. {code}

Add Comment

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau updated an issue

Jenkins / JENKINS-51307 Declarative pipeline and docker entrypoint Change By: Frederic Rousseau

I write a dead simple Dockerfile {code:java} FROM openjdk:8-jdk-alpine ENTRYPOINT "java" {code} I write a dead simple declarative pipeline {code:java} pipeline {     agent { dockerfile true }     stages {         stage('Dead Simple') {             steps {                 checkout scm             }         }     } }{code} I get an error. I get the same error with  {code:java} pipeline {

agent { docker { image 'openjdk:8-jdk-alpine' } }

stages {         stage('Dead Simple') {             steps {                 checkout scm             }         }     } }{code} The error is {code:java} ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`. {code} I cannot pass --entrypoint to the run command, it's jenkins that calls it a bit more logs : {code:java} [Pipeline] withDockerContainer Jenkins does not seem to be running inside a container $ docker run -t -d -u 107:111 -w /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA:rw,z -v /var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:/var/lib/jenkins/workspace/oh-pr0009-api_master-IFYDNFODANQT2HMWSAOO6P6UKZZUCWSO2LNM2M6G7DUPGPLNH7HA@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** 4d6ffe9d9713df374dd2670073b9ea32598df407 cat $ docker top 13d063e7996ad4476075baf7586aa3186d0bff08cdbd4c10205327bb6b44c75b -eo pid,comm ERROR: The container started but didn't run the expected command. Please double check your ENTRYPOINT does execute the command passed as docker run argument, as required by official docker images (see https://github.com/docker-library/official-images#consistency for entrypoint consistency requirements). Alternatively you can force image entrypoint to be disabled by adding option `--entrypoint=''`. {code}

Add Comment

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau assigned an issue to Jesse Glick

Jenkins / JENKINS-51307 Declarative pipeline and docker entrypoint

Change By: Frederic Rousseau Assignee: vjuranek Jesse Glick

Add Comment

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau updated an issue

Jenkins / JENKINS-51307 Declarative pipeline and docker entrypoint

Change By: Frederic Rousseau Component/s: docker-workflow-plugin Component/s: docker-build-step-plugin

Add Comment

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint Hey Jesse, I saw you were working on this plugin and took the liberty to assign you this issue. When I first opened it, I chose the wrong component. The right one is docker-workflow-plugin. Cheers

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick resolved as Not A Defect

As noted in the error message, this is not a valid entrypoint.

Jenkins / JENKINS-51307

Declarative pipeline and docker entrypoint

Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect

Add Comment

[michal.matyjek@gmail.com (JIRA)]

Michal Matyjek commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint It seems with these changes we are making things more complex. What could have been a simple purpose-built container to perform very specific task (regardless if ran on Jenkins or wherever) now requires extra scripting to meet https://github.com/docker-library/official-images#consistency I would argue that some containers used in pipelines will never become official. Anyways, I'd like to leave my solution here in case someone hits this issue: I used to have in my Dockerfile: ENTRYPOINT [ "python", "./my_script.py" ] To make it work, added a new script (`./entrypoint,sh`): #!/bin/sh set -e # check if there was a command passed # required by Jenkins Docker plugin: https://github.com/docker-library/official-images#consistency if [ "$1" ]; then # execute it exec "$@" fi # else run my script exec python ./my_script.py And changed the Dockerfile: ADD entrypoint.sh / ENTRYPOINT [ "/entrypoint.sh" ] You people are smart, you can come with nicer solutions. But I got that goin' for me, which is nice. Thanks Jesse Glick and others for all the hard work on this stuff!

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

you can come with nicer solutions It is being worked on. The withDockerContainer step (including its agent docker Declarative sugar) should be avoided I think; it just never worked consistently enough to be an advertised feature.

Add Comment

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau reopened an issue

Jenkins / JENKINS-51307

Declarative pipeline and docker entrypoint

Change By: Frederic Rousseau Resolution: Not A Defect Status: Resolved Reopened Assignee: Jesse Glick Carlos Sanchez

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[zougi.fr@gmail.com (JIRA)]

Frederic Rousseau commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint Carlos Sanchez what do you think about this issue? docker maven doesn't work out of the box on declarative pipeline https://github.com/carlossg/docker-maven/  Michal Matyjek, your solution I find intrusive. I prefer to do the following to build my dockers. It's Ugly but the problem comes from Jenkins, I prefer to fix it in Jenkinsfile     agent {         dockerfile {             args '--entrypoint=\'\''         }     }

Add Comment

[pieter@pietervogelaar.nl (JIRA)]

Pieter Vogelaar edited a comment on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

Thanks [~zougi], I search searched a lot on the internet and I finally found this Jira issue. I couldn't understand why nginx wasn't listening inside the container. But I guess Jenkins doesn't execute by default the entrypoint/CMD of de Docker image. This fixed it for me: {code:java} customImage.inside("-u root --entrypoint='/start.sh'") {} {code}

Add Comment

[pieter@pietervogelaar.nl (JIRA)]

Pieter Vogelaar commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

Thanks Frederic Rousseau, I search a lot on the internet and I finally found this Jira issue. I couldn't understand why nginx wasn't listening inside the container. But I guess Jenkins doesn't execute by default the entrypoint/CMD of de Docker image. This fixed it for me:

customImage.inside("-u root --entrypoint='/start.sh'") {}

Add Comment

[owen@nerdnetworks.org (JIRA)]

Owen Mehegan commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

We have seen in two different cases that upgrading to 1.15.1 fixes this issue.

Add Comment

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

[owen@nerdnetworks.org (JIRA)]

[owen@nerdnetworks.org (JIRA)]

Owen Mehegan updated an issue

Jenkins / JENKINS-51307

Declarative pipeline and docker entrypoint

Change By: Owen Mehegan Comment:

We have seen in two different cases that upgrading to 1.15.1 fixes this issue.

Add Comment

[sschuberth@gmail.com (JIRA)]

Sebastian Schuberth commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint Note that https://github.com/docker-library/official-images#consistency, point 3, says "If the image only contains the main executable and its linked libraries (ie no shell) then it is fine to use the executable as the ENTRYPOINT". So using cat as the command is not a valid consistency check. How can I just run the defined ENTRYPOINT, optionally passing arguments, but not have any steps defined?

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

How can I just run the defined ENTRYPOINT, optionally passing arguments, but not have any steps defined? sh 'docker run --rm my-image some-arg'

Add Comment

[timblaktu@gmail.com (JIRA)]

Tim Black commented on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

Sebastian Schuberth, regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful. For example, the following pipeline code:   docker_image.inside("<other args>")  {   ... }   results in the following docker run command, which has inserted a cat command at the end.    docker run -t -d -u 118:124 <other args...> <image-name> cat     I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[timblaktu@gmail.com (JIRA)]

Tim Black edited a comment on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

[~sschuberth], regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful.

For example, the following pipeline code:

{code:java} docker_image.inside("<other args>")  {   ... }{code}

results in the following docker run command, which has inserted a {{cat}} command at the end.

{code:java} docker run -t -d -u 118:124 <other args...> <image-name> cat    {code}

I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance?

Add Comment

[timblaktu@gmail.com (JIRA)]

Tim Black edited a comment on JENKINS-51307

Re: Declarative pipeline and docker entrypoint

[~sschuberth], regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful. For example, the following pipeline code:   {code:java} docker_image.inside("<other args>")  {   ... }{code}   results in the following docker run command, which has inserted a {{cat}} command at the end.    {code:java} docker run -t -d -u 118:124 <other args...> <image-name> cat    {code} I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance?

UPDATE: I have since found this PR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/116] which discussion confirms the explicit forcing of CMD to `cat`. It is still woefully unclear to me how to specify, in a Dockerfile, how to run a command every time the docker image is run, when using Jenkins/Docker "inside()" pipeline.

Add Comment