After Upgrading Docker Pipeline Plugin from 1.4 to latest(1.7), our pipeline job running with Docker started failing with following error,
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
for entrypoint best practices.[Pipeline]
$ docker stop --time=1 6c3e4c47264e7766c2277555ac05de7267ab0895ab8f91b257761a6c649379c2
$ docker rm -f 6c3e4c47264e7766c2277555ac05de7267ab0895ab8f91b257761a6c649379c2[Pipeline] // withDockerContainer[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // ws[Pipeline] }[Pipeline] // node[Pipeline] echoError: hudson.AbortException: script returned exit code -2
Investigating further we found that issue is with Docker Pipeline Plugin 1.5.
Can you please help us fix this issue? Are we missing something while using version 1.5 or is it a bug in the plugin?
|Assignee||Carroll Chiou [ carroll ]|
|Resolution||Fixed [ 1 ]|
|Status||Open [ 1 ]||Fixed but Unreleased [ 10203 ]|
|Status||Fixed but Unreleased [ 10203 ]||Resolved [ 5 ]|