-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 2.189
When I update the Pipeline: Nodes and Processes plugin from 2.30 to 2.33 our pipelines stop working with the following error:
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/path/to/workspace/folder") set in config.json failed: no such file or directory": unknown
This happens in the following part of our Jenkinsfile:
stage('Install dependencies') { node('docker') { ansiColor('xterm') { exws(extWorkspace) { composer: { composer.inside("-v ${caches}/npm:/srv/jenkins/.npm:rw") { sh 'npm install' } } } }} }
It works on version 2.30.
Note that I cut out the part where composer dependencies get installed, since it already crashes on npm install.
[JENKINS-58963] OCI runtime exec failed after updating Pipeline: Nodes and Processes to 2.33
Thomas Buys
created issue -
Thomas Buys
made changes -
| Description |
Original:
When I update the [Pipeline: Nodes and Processes|https://plugins.jenkins.io/workflow-durable-task-step] plugin from 2.30 to 2.33 our pipelines stop working with the following error: OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/path/to/workspace/folder") set in config.json failed: no such file or directory": unknown This happens in the following part of our Jenkinsfile: {code:java} stage('Install dependencies') { node('docker') { ansiColor('xterm') { exws(extWorkspace) { composer: { composer.inside("-v ${caches}/npm:/srv/jenkins/.npm:rw") { sh 'npm install' } } } }} } {code} It works on version 2.30. |
New:
When I update the [Pipeline: Nodes and Processes|https://plugins.jenkins.io/workflow-durable-task-step] plugin from 2.30 to 2.33 our pipelines stop working with the following error: {code:java} OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/path/to/workspace/folder") set in config.json failed: no such file or directory": unknown{code} This happens in the following part of our Jenkinsfile: {code:java} stage('Install dependencies') { node('docker') { ansiColor('xterm') { exws(extWorkspace) { composer: { composer.inside("-v ${caches}/npm:/srv/jenkins/.npm:rw") { sh 'npm install' } } } }} } {code} It works on version 2.30. |
Thomas Buys
made changes -
| Description |
Original:
When I update the [Pipeline: Nodes and Processes|https://plugins.jenkins.io/workflow-durable-task-step] plugin from 2.30 to 2.33 our pipelines stop working with the following error: {code:java} OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/path/to/workspace/folder") set in config.json failed: no such file or directory": unknown{code} This happens in the following part of our Jenkinsfile: {code:java} stage('Install dependencies') { node('docker') { ansiColor('xterm') { exws(extWorkspace) { composer: { composer.inside("-v ${caches}/npm:/srv/jenkins/.npm:rw") { sh 'npm install' } } } }} } {code} It works on version 2.30. |
New:
When I update the [Pipeline: Nodes and Processes|https://plugins.jenkins.io/workflow-durable-task-step] plugin from 2.30 to 2.33 our pipelines stop working with the following error: {code:java} OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/path/to/workspace/folder") set in config.json failed: no such file or directory": unknown{code} This happens in the following part of our Jenkinsfile: {code:java} stage('Install dependencies') { node('docker') { ansiColor('xterm') { exws(extWorkspace) { composer: { composer.inside("-v ${caches}/npm:/srv/jenkins/.npm:rw") { sh 'npm install' } } } }} } {code} It works on version 2.30. Note that I cut out the part where composer dependencies get installed, since it already crashes on npm install. |
| Component/s | New: docker-workflow-plugin [ 20625 ] | |
| Component/s | Original: workflow-durable-task-step-plugin [ 21715 ] |