Containers are created but not used

• docker-plugin version 1.1.6
• Jenkins ver. 2.176.1
• Docker version 18.06.1-ce

I’m trying to run a simple git clone command inside a container (jenkins-ssh), which is on another host (slave host): pipeline { agent {label ‘slave1’} stages { stage(‘GetCode’) { steps { sh ‘git clone myrepo.git’ } …

The problem is that although container are created successfully, docker ps + docker logs. The jenkins UI shows the message that “Queued All nodes of label ‘slave1’ are offline”.

Jenkins logs are showing the following:

INFO: Trying to run container for node slave1-0007qgo2yrd6u from image: jenkins/ssh-slave
Jul 03, 2019 1:39:18 PM com.nirima.jenkins.plugins.docker.DockerTemplate doProvisionNode
INFO: Started container ID 42bac5ecbe3e6b81bfc25822d62a542628745c602198e80ef7fdbe68bfdc95b0 for node slave1-0007qgo2yrd6u from image: jenkins/ssh-slave
Jul 03, 2019 1:39:19 PM com.nirima.jenkins.plugins.docker.utils.PortUtils$ConnectionCheckSSH execute
INFO: SSH port is open on 192.168.1.18:32846
Jul 03, 2019 1:39:27 PM hudson.slaves.NodeProvisioner$2 run
INFO: Image of jenkins/ssh-slave provisioning successfully completed. We have now 31 computer(s)
Jul 03, 2019 1:39:27 PM com.nirima.jenkins.plugins.docker.DockerCloud provision
INFO: Asked to provision 1 slave(s) for: slave1
Jul 03, 2019 1:39:27 PM com.nirima.jenkins.plugins.docker.DockerCloud canAddProvisionedSlave
INFO: Provisioning 'jenkins/ssh-slave' on 'docker'; Total containers: 30 (of 100)
Jul 03, 2019 1:39:27 PM com.nirima.jenkins.plugins.docker.DockerCloud provision
INFO: Will provision 'jenkins/ssh-slave', for label: 'slave1', in cloud: 'docker'
Jul 03, 2019 1:39:27 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply
INFO: Started provisioning Image of jenkins/ssh-slave from docker with 1 executors. Remaining excess workload: 0
Jul 03, 2019 1:39:27 PM com.nirima.jenkins.plugins.docker.DockerTemplate pullImage
INFO: Pulling image 'jenkins/ssh-slave:latest'. This may take awhile...
Jul 03, 2019 1:39:28 PM com.nirima.jenkins.plugins.docker.DockerTemplate pullImage
INFO: Finished pulling image 'jenkins/ssh-slave:latest', took 1115 ms
Jul 03, 2019 1:39:28 PM com.nirima.jenkins.plugins.docker.DockerTemplate doProvisionNode
INFO: Trying to run container for jenkins/ssh-slave
Jul 03, 2019 1:39:28 PM com.nirima.jenkins.plugins.docker.DockerTemplate doProvisionNode
INFO: Trying to run container for node slave1-0007qgsnyzliy from image: jenkins/ssh-slave
Jul 03, 2019 1:39:28 PM com.nirima.jenkins.plugins.docker.DockerTemplate doProvisionNode
INFO: Started container ID 5a3f082985eac8305334389600bf64ca7413816ee5bc16b3707ba8cc9d11a59c for node slave1-0007qgsnyzliy from image: jenkins/ssh-slave

So basically, containers are provisioned but nothing is executed inside them.

[pjdarton]

Yup, that’s the way the SSH-Inject method works. No further steps required.

However, you will need to ensure that the filesystem location into which the plugin puts the key is the same location that the SSH service will be looking for one, and that the ownership etc is correct etc, otherwise the SSH service won’t let Jenkins log in.

[pjdarton]

Re: “Amazon Linux” Another “hard won” lesson I learned is that you have to be careful when mixing different Javas. I found that Oracle & OpenJDK weren’t fussy - as long as the major versions were the same, you could have any Oracle running master & any OpenJDK on the slaves, or the other way around but I found that if I was using the IBM Java I had to ensure that I used exactly the same version (including patches etc) everywhere. I’ve never used/tried Amazon Linux but I would suggest that you use OpenJDK 8 (or higher) everywhere as that’s what Jenkins is built, tested & supported on.