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.
That's kind of my point. If we're referring to the command, we should be explicit: Building the container with `create` will now initialize the volume.

If not, @thaJeztah's revision is probably better than mine.