• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: docker-workflow-plugin
• Labels:

  None
• Environment:

  jenkins 2.287
  docker-plugin: 1.2.2
  docker-workflow: 1.2.6

[JENKINS-65545] env vars are not consistent

Stanislav Pugachov created issue - 2021-05-05 09:58

Stanislav Pugachov made changes - 2021-05-05 10:20

Description

Original: I'm trying to do something like this: {code:java} node {     stage('reproduce') {         sh """             echo '1'             printenv PATH             echo "$PATH"         """         docker.image('python:3.6.4-slim').inside {             sh """                 echo '2'                 printenv PATH                 echo "$PATH"             """             withEnv(["PATH=$PATH:/my/custom/path"]) {                 sh """                     echo '3'                     printenv PATH                     echo "$PATH"                 """             }         }     } } {code} sh (1) gives me: {noformat} + printenv PATH /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + echo /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin{noformat} all is good so far sh (2) gives me: {noformat} + printenv PATH /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + echo /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin{noformat} which is already confusing sh (3) gives: {noformat} + printenv PATH /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + echo /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/my/custom/path /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/my/custom/path{noformat}   I have couple of questions about this:  * why printenv and echo in sh(2) show different results? sounds like printenv prints original env which comes from docker image while echo prints value from host jenkins.  * why withEnv which is executed inside docker container does not modify docker's PATH but modifies Jenkins's PATH.

New: I'm trying to do something like this: {code:java} node {     stage('reproduce') {         sh """             echo '1'             printenv PATH             echo "$PATH"         """         docker.image('python:3.6.4-slim').inside {             sh """                 echo '2'                 printenv PATH                 echo "$PATH"             """             withEnv(["PATH=$PATH:/my/custom/path"]) {                 sh """                     echo '3'                     printenv PATH                     echo "$PATH"                 """             }         }     } } {code} sh (1) gives me: {noformat} + printenv PATH /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + echo /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin{noformat} all is good so far sh (2) gives me: {noformat} + printenv PATH /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + echo /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin{noformat} which is already confusing sh (3) gives: {noformat} + printenv PATH /usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + echo /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/my/custom/path /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/my/custom/path{noformat}   I have couple of questions about this:  * why printenv and echo in sh(2) show different results? sounds like printenv prints original env which comes from docker image while echo prints value from host jenkins.  * why withEnv which is executed inside docker container does not modify docker's PATH but modifies Jenkins's PATH.

Collapse comment: Martin added a comment - 2021-05-06 19:12

Martin added a comment - 2021-05-06 19:12

This also does not work for us. But we use a workaround like

sh makeEnvList(envList) + ' echo "$PATH" '

...

String makeEnvList(env){
String s = '\n'
for(int i = 0; i < env.size(); i++)
s += 'export ' + env[i]
return s
}

Ps. Written on my phone keyboard. Therefore is possible that the snippet has wrong syntax. But I think like example it is enough.

Expand comment: Martin added a comment - 2021-05-06 19:12

Martin added a comment - 2021-05-06 19:12 This also does not work for us. But we use a workaround like sh makeEnvList(envList) + ' echo "$PATH" ' ... String makeEnvList(env){ String s = '\n' for(int i = 0; i < env.size(); i++) s += 'export ' + env [i] return s } Ps. Written on my phone keyboard. Therefore is possible that the snippet has wrong syntax. But I think like example it is enough.