• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: docker-custom-build-environment-plugin
• Labels:

  • plugin
• Environment:

  Jenkins 1.639
  docker-custom-build-environment:1.6.4

1. 

   container_start_command.png

   10 kB

   2015-12-11 10:35

[JENKINS-32010] Container start command option - Argument parsing

Paris Zoumpouloglou created issue - 2015-12-10 16:56

Paris Zoumpouloglou made changes - 2015-12-10 16:58

Description

Original: This bug concerns container start commands with one or more command line options. If a container is run from command line like : {{docker run -it <image_hash> "tail -n 20 /etc/passwd" }} the "tail -n 20 /etc/passwd" command is interpreted as: {{ "Path": "/bin/sh",     "Args": [         "-c",         "tail -n 20 /etc/passwd"     ],}} However if I add the same command without quotes in "Container start command" option it is interpreted as : {{ "Path": "/bin/sh",     "Args": [         "-c",         "tail",         "-n",         "20",         "/etc/passwd"     ],}} If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) : {{ "Path": "/bin/sh",     "Args": [         "-c",         "'tail",         "-n",         "20",         "/etc/passwd'"     ], }} Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option.

New: This bug concerns container start commands with one or more command line options. If a container is run from command line like : docker run -it <image_hash> "tail -n 20 /etc/passwd" the "tail -n 20 /etc/passwd" command is interpreted as:     "Path": "/bin/sh",     "Args": [         "-c",         "tail -n 20 /etc/passwd"     ], However if I add the same command without quotes in "Container start command" option it is interpreted as :     "Path": "/bin/sh",     "Args": [         "-c",         "tail",         "-n",         "20",         "/etc/passwd"     ], If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) :     "Path": "/bin/sh",     "Args": [         "-c",         "'tail",         "-n",         "20",         "/etc/passwd'"     ], Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option.

Paris Zoumpouloglou made changes - 2015-12-10 17:07

Description

Original: This bug concerns container start commands with one or more command line options. If a container is run from command line like : docker run -it <image_hash> "tail -n 20 /etc/passwd" the "tail -n 20 /etc/passwd" command is interpreted as:     "Path": "/bin/sh",     "Args": [         "-c",         "tail -n 20 /etc/passwd"     ], However if I add the same command without quotes in "Container start command" option it is interpreted as :     "Path": "/bin/sh",     "Args": [         "-c",         "tail",         "-n",         "20",         "/etc/passwd"     ], If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) :     "Path": "/bin/sh",     "Args": [         "-c",         "'tail",         "-n",         "20",         "/etc/passwd'"     ], Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option.

New: This bug concerns container start commands with one or more command line options. If a container is run from command line like : {code:java} docker run -it <image_hash> "tail -n 20 /etc/passwd" {code} the "tail -n 20 /etc/passwd" command is interpreted as: {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "tail -n 20 /etc/passwd"     ], {code} However if I add the same command without quotes in "Container start command" option it is interpreted as : {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "tail",         "-n",         "20",         "/etc/passwd"     ], {code} If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) : {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "'tail",         "-n",         "20",         "/etc/passwd'"     ], {code} Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option.

Paris Zoumpouloglou made changes - 2015-12-11 10:37

Attachment		New: container_start_command.png [ 31428 ]
Environment		New: Jenkins 1.639 docker-custom-build-environment:1.6.4
Summary	Original: Container start command argument parsing	New: Container start command option - Argument parsing

Paris Zoumpouloglou made changes - 2015-12-11 12:27

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Paris Zoumpouloglou made changes - 2015-12-11 12:27

Status

Original: In Progress [ 3 ]

New: Open [ 1 ]

Paris Zoumpouloglou made changes - 2015-12-11 12:39

Description

Original: This bug concerns container start commands with one or more command line options. If a container is run from command line like : {code:java} docker run -it <image_hash> "tail -n 20 /etc/passwd" {code} the "tail -n 20 /etc/passwd" command is interpreted as: {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "tail -n 20 /etc/passwd"     ], {code} However if I add the same command without quotes in "Container start command" option it is interpreted as : {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "tail",         "-n",         "20",         "/etc/passwd"     ], {code} If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) : {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "'tail",         "-n",         "20",         "/etc/passwd'"     ], {code} Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option.

New: This bug concerns container start commands with one or more command line options. If a container is run from command line like : {code:java} docker run -it <image_hash> "tail -n 20 /etc/passwd" {code} the "tail -n 20 /etc/passwd" command is interpreted as: {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "tail -n 20 /etc/passwd"     ], {code} However if I add the same command without quotes in "Container start command" option it is interpreted as : {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "tail",         "-n",         "20",         "/etc/passwd"     ], {code} If I enclose the command in single or double quotes the problem remains since the command is interpreted as (example using single quotes) : {code:java}     "Path": "/bin/sh",     "Args": [         "-c",         "'tail",         "-n",         "20",         "/etc/passwd'"     ], {code} Both cases result in errors and the container does not start. I searched through the documentation but there are no recommendations regarding this option.

Nicolas De Loof made changes - 2016-02-29 13:15

Priority

Original: Blocker [ 1 ]

New: Minor [ 4 ]

R. Tyler Croy made changes - 2016-07-25 23:52

Workflow

Original: JNJira [ 167483 ]

New: JNJira + In-Review [ 182754 ]

Nicolas De Loof made changes - 2019-04-24 14:29

Assignee

Original: Nicolas De Loof [ ndeloof ]