No Containers being spawned about docker-plugin HOT 6 CLOSED

Sounds a lot like #50

from docker-plugin.

Are you still having problems with this? I believe this is actually Jenkins "NodeProvisioner" deciding there is not enough work to be done to justify spinning up a cloud slave. Make sure the build has completely succeeded/failed once and see if the next time it will spin up Docker slaves.

from docker-plugin.

Yes - if I specify a specific label then Jenkins spins up my container.
If I use the same labels as everything else it seems that Jenkins is very reluctant to spin up a container.
Even sometimes appearing to refuse to spin one up even when all 'physical' slaves are busy.

from docker-plugin.

I am curious what the queue length looks like in the Load Statistics screen. Based on what I have read, Jenkins should try to spin up a slave if it is greater than 1, but it is also dampened to prevent spinning up slaves for a single job if it can avoid it.

If Jenkins does want to spin one up and the docker plugin says it has a compatible container, it will be logged as "Excess workload" just before attempting to start a container (which may fail if it is at the limit).

from docker-plugin.

Is it still actual?

from docker-plugin.

Closed by mistake 😃 but feel free to reopen if issue is still valid

from docker-plugin.