R. Tyler Croy added a comment - 2018-02-07 23:34 As best as I can tell from my research it looks like a container ID is being generated inside the Docker code which doesn't actually match the name of the container on the host? Quite perplexed.

R. Tyler Croy added a comment - 2018-02-08 01:51 In further testing I was able to reproduce this in a pristine environment with the Jenkinsfile used by jenkinsci/docker . It seems like a simple use case such as the following works fine with 1.15: node { docker.image( 'node:alpine' ).inside { sh 'pwd' } } When I used the same container being used in jenkinsci/docker , koalaman/shellcheck:v0.4.6 I reproduced the error, with the following log output: Started by user admin Replayed #2 Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on Jenkins in / var /jenkins_home/workspace/example [Pipeline] { [Pipeline] sh [example] Running shell script + docker inspect -f . koalaman/shellcheck:v0.4.6 . [Pipeline] withDockerContainer Jenkins seems to be running inside container 439d08e94a52ab7b4b298fa60194c16ac5406ab6eb6aa32cacb7c714ea775c70 $ docker run -t -d -u 0:0 -w / var /jenkins_home/workspace/example --volumes-from 439d08e94a52ab7b4b298fa60194c16ac5406ab6eb6aa32cacb7c714ea775c70 -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** koalaman/shellcheck:v0.4.6 cat $ docker top a224b71731d78d747d4290a34ca6c178fdcccc0863800213323c990d4b9fa654 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. See https: //docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#entrypoint for entrypoint best practices. [Pipeline] { [Pipeline] sh [example] Running shell script Error response from daemon: Container a224b71731d78d747d4290a34ca6c178fdcccc0863800213323c990d4b9fa654 is not running [Pipeline] } $ docker stop --time=1 a224b71731d78d747d4290a34ca6c178fdcccc0863800213323c990d4b9fa654 $ docker rm -f a224b71731d78d747d4290a34ca6c178fdcccc0863800213323c990d4b9fa654 [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code -2 Finished: FAILURE What's interesting to me is that there is an ENTRYPOINT error message in this log. The same container, executing on ci.jenkins.io with Docker Pipeline 1.15, has this log output: Started by user rtyler Connecting to https: //api.github.com using jenkinsadmin/****** (GitHub access token for jenkinsadmin) Loading trusted files from base branch master at f5859db6513c6f4ce1d687a5cbd75556ca884c64 rather than aa517f2db161c52bee8c6bbd083ff9a10abe18e4 Obtained Jenkinsfile from f5859db6513c6f4ce1d687a5cbd75556ca884c64 Running in Durability level: MAX_SURVIVABILITY Loading library pipeline-library@master Attempting to resolve master from remote references... Found match: refs/heads/master revision ec29bbe966194298de7db8b323a816986e8a8f47 Fetching changes from the remote Git repository Fetching without tags Checking out Revision ec29bbe966194298de7db8b323a816986e8a8f47 (master) Commit message: "Merge pull request #24 from jglick/jdk-stage-fix" [Pipeline] properties [Pipeline] timeout Timeout set to expire in 20 min [Pipeline] { [Pipeline] node Still waiting to schedule task Waiting for next available executor on docker Running on ubuntu-jenkinsinfra4c19b0 in /home/jenkins/workspace/Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ [Pipeline] { [Pipeline] deleteDir [Pipeline] stage [Pipeline] { (Checkout) [Pipeline] checkout Cloning the remote Git repository Cloning with configured refspecs honoured and without tags remote: Counting objects remote: Compressing objects Receiving objects Resolving deltas Updating references Fetching without tags Merging remotes/origin/master commit f5859db6513c6f4ce1d687a5cbd75556ca884c64 into PR head commit aa517f2db161c52bee8c6bbd083ff9a10abe18e4 Merge succeeded, producing 8c05e8acb4f147d44292a0c103fddc8b25d6ce92 Checking out Revision 8c05e8acb4f147d44292a0c103fddc8b25d6ce92 (PR-631) Commit message: "Merge commit 'f5859db6513c6f4ce1d687a5cbd75556ca884c64' into HEAD" First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (shellcheck) [Pipeline] sh [Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ] Running shell script + docker inspect -f . koalaman/shellcheck:v0.4.6 Error: No such object: koalaman/shellcheck:v0.4.6 [Pipeline] sh [Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ] Running shell script + docker pull koalaman/shellcheck:v0.4.6 v0.4.6: Pulling from koalaman/shellcheck 627beaf3eaaf: Pulling fs layer 02712c44beac: Pulling fs layer 366df5cfa23a: Pulling fs layer 366df5cfa23a: Verifying Checksum 366df5cfa23a: Download complete 627beaf3eaaf: Verifying Checksum 627beaf3eaaf: Download complete 02712c44beac: Verifying Checksum 02712c44beac: Download complete 627beaf3eaaf: Pull complete 02712c44beac: Pull complete 366df5cfa23a: Pull complete Digest: sha256:191b61e5f436fc51f22faaf2f4e0f77799f75977c7210377dd73a1a0f99ef8bd Status: Downloaded newer image for koalaman/shellcheck:v0.4.6 [Pipeline] withDockerContainer ubuntu-jenkinsinfra4c19b0 does not seem to be running inside a container $ docker run -t -d -u 1000:1000 -w /home/jenkins/workspace/Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ -v /home/jenkins/workspace/Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ:/home/jenkins/workspace/Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ:rw,z -v /home/jenkins/workspace/Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ@tmp:/home/jenkins/workspace/Packaging_docker_PR-631-CBEVRL6YSXR25EYNHKWGBQCR2ZTCISJQY2B5SQLHV3W4GLKRZYZQ@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 ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** koalaman/shellcheck:v0.4.6 cat $ docker top 45fbd92fef01633fe08c09cb73d65e70baaa66c6ffa5809f8665ff7d17539052 [Pipeline] // withDockerContainer [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // timeout [Pipeline] End of Pipeline GitHub has been notified of this commit’s build result java.io.IOException: Failed to run top '45fbd92fef01633fe08c09cb73d65e70baaa66c6ffa5809f8665ff7d17539052' . Error: Error response from daemon: Container 45fbd92fef01633fe08c09cb73d65e70baaa66c6ffa5809f8665ff7d17539052 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) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/ var /jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:135) at org.jenkinsci.plugins.docker.workflow.Docker.node(jar:file:/ var /jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:66) at org.jenkinsci.plugins.docker.workflow.Docker$Image.inside(jar:file:/ var /jenkins_home/plugins/docker-workflow/WEB-INF/lib/docker-workflow.jar!/org/jenkinsci/plugins/docker/workflow/Docker.groovy:123) at WorkflowScript.run(WorkflowScript:21) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor223.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ClosureBlock.eval(ClosureBlock.java:46) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:35) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:32) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:32) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:331) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:82) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:243) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:231) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang. Thread .run( Thread .java:748) Finished: FAILURE Note the lack of error message about ENTRYPOINT. Of course,when I downgrade the plugin on ci.jenkins.io to Docker Pipeline 1.14, the same exact Pipeline with the same exact koalaman/shellcheck:v0.4.6 container succeeds. Perplexed!

R. Tyler Croy added a comment - 2018-02-13 16:33 I think this might be a duplicate of JENKINS-49278 . Will test with the new 1.15.1 release to verify

Nicolas De Loof added a comment - 2018-02-13 16:45 it seems so indeed. 1.15.1 won't fix this by magic, you might have to pass extra arg `–entrypoint=""` if image's entrypoint isn't designed as recommended by docker for official images.

R. Tyler Croy added a comment - 2018-02-13 16:46 Tested with a 1.5.1 .hpi downloaded from repo.jenkins-ci.org, still the same error with this Pipeline: node { docker.image( 'koalaman/shellcheck:v0.4.6' ).inside { sh 'pwd' } } (simialr to this Jenkinsfile )

R. Tyler Croy added a comment - 2018-02-13 16:49 ndeloof , I'm trying to understand more whether this is a bug or whether this is a breaking change which should be very broadly communicated. As I referenced in my previous comment, this Jenkinsfile has worked for a long-long time, and works with 1.14. As of 1.15 this Pipeline now breaks. If the solution is to add `--entrypoint=""`, then could the Docker Pipeline plugin simply doi that automatically?