Flood Docker slaves IDLE about docker-plugin HOT 5 CLOSED

I also observe the same comportment and haven't been able to track-it down.

In fact, I'd like to be able to enable this as a feature, so Jenkins could "preload" the slaves (within the max container or max instance limit), reducing the cloud plugin overhead when starting a lot of jobs at the same time.

(Jenkins 1.567, Docker 1.0.0 on CentOS 6)

from docker-plugin.

I need to do more investigating, which will probably involve building the plugin myself. But I believe what is happening is that jobs with no label restriction are causing a docker container to be provisioned. The logic in the DockerCloud is to use the first container when a null label is requested, thus they are all the same container getting provisioned. However, for some reason, Jenkins thinks the provisioned slave is not satisfactory and will not send the job to it. Even worse, the Docker retention policy will not terminate an idle slave if it has not done work.

from docker-plugin.

Here is a question for you. We are discussing on #59, whether it is worth having the "Utilize node as much as possible"/"Tied jobs only" option on containers. Alternatively should it be hard coded one way or another?

from docker-plugin.

Thanks alot for these fix ! can't wait to test them :) !!!

from docker-plugin.

Fixed in 0.7 release.

from docker-plugin.