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.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>

docs/sources/reference/api/docker_remote_api.md

@@ -57,6 +57,9 @@ total memory available (`MemTotal`).
 **New!**
 You can set the new container's MAC address explicitly.
 
+**New!**
+Volumes are now initialized when the container is created.
+
 `POST /containers/(id)/start`
 
 **New!**