-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.104 on Docker 17.10.0-ce on CentOS 7.4.1708 (Kernel 3.10.0-693.2.2.el7.x86_64)
When using a declarative Jenkins pipeline with a stage that uses a Docker agent, I get a confusing error message in the Jenkins log:
$ docker top 08e1c013e07083492ad0f03285f1a7d30063fb15e0cf39be7b55af6d1a03c829 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.
The build continues normally and the cat command is actually running inside the container, so everything is fine except that the error message occurs although it shouldn't.
Comparing the code in listProcess in https://github.com/jenkinsci/docker-workflow-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/workflow/client/DockerClient.java with the output of docker top shows the likely cause of that error:
docker top prints the following fields
UID PID PPID C STIME TTY TIME CMD build 19799 19784 0 22:23 pts/0 00:00:00 cat
However, the Java client assumes that only PID, USER, TIME and COMMAND is printed. I suggest that the process list is determined by using an explicit format specifier like
docker container top ${CONTAINER_ID} -eo pid,comm
- duplicates
-
JENKINS-39748 Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
- In Review
- is blocked by
-
JENKINS-49385 containers exit early in docker-workflow 1.15
- Resolved
- is duplicated by
-
JENKINS-49446 Regression with 1.15 and WithContainerStep
- Closed
- relates to
-
JENKINS-49385 containers exit early in docker-workflow 1.15
- Resolved
- links to
- mentioned in
-
Page Loading...