-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.19.3 on a Debian 8, remote slave agents running on empty Debian 8 with only docker
Hi,
I have a weird behavior when I try to use the docker image debian:wheezy. Whatever I try to do inside this container, it looks like docker manager don't wait for the command to be proceed.
Here is the Jenkinsfile I'm using:
#!groovy stage('run') { node('docker') { docker.image('debian:wheezy').inside { sh "sleep 30s" } } }
The image is well pulled and a container is well ran but when it comes to do the sleep command, well, it just pass and return a bad exit code and output
ERROR: script returned exit code -1
If you replace debian:wheezy with anything else like debian:jessie or ubuntu:whatever it works.
Basically, the container don't seems to have any issue by itself but, when used on a Jenkinsfile pipeline using this plugin its seems to be broken. Actually I don't know if the issue is the plugin or the container: enlight me please !
PS: Thx for your amazing job <3
- is duplicated by
-
JENKINS-43881 Jobs run on workers (or in docker containers) without `ps` are silently killed
- Resolved
- is related to
-
JENKINS-46545 Sh block unexpectedly exits with failure in docker
- Resolved
- relates to
-
JENKINS-46969 Docker container closes prematurely
- Resolved
-
JENKINS-35370 Workflow shell step ERROR: script returned exit code -1
- Reopened
-
JENKINS-42166 ProcessLiveness.workingLaunchers heuristic is flaky
- Resolved
- links to