…glas)This PR was merged into the 2.8 branch.Discussion----------[FrameworkBundle] Allow to autowire service_container| Q             | A| ------------- | ---| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#17252| License       | MIT| Doc PR        | n/aCommits-------4e2eef0 [FrameworkBundle] Allow to autowire service_container

…or of other services (weaverryan)This PR was merged into the 2.8 branch.Discussion----------Autowiring the concrete class too - consistent with behavior of other services| Q             | A| ------------- | ---| Branch        | 2.8| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#18132| License       | MIT| Doc PR        | n/aThis follows#17261. Without this, if you use the concrete class `Container`, it doesn't autowire, so it creates a *new* one. That is certainly not what the end-user wants, and it's a serious WTF :). We can talk all day long about not injecting the container and type-hinting interfaces, but this is needed to be consistent with how all the other services in the container work and to avoid this odd behavior.Thanks!Commits-------2ea3f68 Autowiring the concrete class too - consistent with behavior of other services