jenkinsci / jenkinsci/docker-workflow-plugin
[JENKINS-58963] OCI runtime exec failed after updating Pipeline: Nodes and Processes to 2.33
- Dominant language
- Java
- Stars
- 527
- Forks
- 422
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
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.
---
Originally reported by gevalo1, imported from: OCI runtime exec failed after updating Pipeline: Nodes and Processes to 2.33
Raw content of original issue
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.
- environment:
Jenkins ver. 2.189
Contributor guide
Assessment
This issue has not been assessed yet.