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.
Really people want to `docker create -v /foo --name myfoo ... && docker --volumes-from myfoo`
And in general, especially since `docker create` exists, it's a little weird to have containers around that you can't use the volumes from because they've never actually been started.