If using a Cloud (ie docker) type slaves, implied labels that refer to labels defined in the Cloud configuration do not work (No nodes that match expression).

Steps to reproduce problem:

1. Install docker plugin
2. Define a new Cloud in Jenkins main config
3. Define a new Docker template in the new cloud and assign it some labels (ie "docker")
4. Create a new implied label, ie "container" -> "docker"
5. Restrict any job to run on label "container"
6. Run job (never executes since there are no matching nodes)

It is possible that you do not even need to configure the Cloud with valid values for this test.

Workaround for simple aliasing:

Instead of using implied labels, add "container" directly to every docker template definition.