I'm seeing this problem as well.
At some point Jenkins stops creating docker slaves. The queue shows all
nodes of label 'docker' are offline, and the appropriate docker slave is
not initialized. Restarting Jenkins fixes the problem for a while.
Docker plugin 0.8, Jenkins 1.585. We've seen this
we found the latest jenkins and docker plugin work better together. Older
versions would not always fire up a slave when they where supposed to - or
fired up the wrong slave type!
if you can upgrade to the next soon to be stable LTS and give it a go you
may find it works better.
On Tuesday,
All,
I am using the docker-plugin and provisioning containers as I require them.
I am using the latest LTS Jenkins release.
I have some non cloud based slaves with a label of ubuntu_12.04 and I also
use this label for the docker containers.
If I take all the non-cloud slaves offline (which is
How long have you waited for it to start a new node? I've found it can take
quite a while (minutes) which apparently is caused by
https://issues.jenkins-ci.org/browse/JENKINS-24752. Not sure if thats the
case in your instance though.
If you have a label which only contains docker providers does
