Initialize volumes when container is created

Fixes #8942
Current behavior is that volumes aren't initialized until start.
Volumes still need to be initialized on start since VolumesFrom and
Binds can be passed in as part of HostConfig on start, however anything
that's already been initialized will just be skipped as is the current
behavior.
I'm not sure this will be right to do.  We may have to break up the code within this function so that we go through the volumes and do the create without the other actions involved.