[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly

[dannyguint...@gmail.com (JIRA)]

Title: Message Title

Danny Guinther commented on JENKINS-49278   Re: cat command in docker agents not detected correctly I'm also still seeing this issue after upgrading to 1.15.1:   $ docker top d720fd88f4be924edf76e1d55bc058d82dce45f8cb4a34eb2db492b380fe1ab5 -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=''`.     Here's the result of `docker top d720fd88f4be924edf76e1d55bc058d82dce45f8cb4a34eb2db492b380fe1ab5 -eo pid,comm`     $ docker top d720fd88f4be924edf76e1d55bc058d82dce45f8cb4a34eb2db492b380fe1ab5 -eo pid,comm PID COMMAND 123094 init 123133 cat 123212 sh 123218 sh 123219 script.sh 123221 test 123252 npm 123431 sleep     `cat` is clearly in the list.   I also tried removing the `–init` option passed to the container in case `cat` needed to be first in the list, it didn't resolve the issue.    Please let me know if I can offer any other diagnostic info. 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.