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>
graphdb: initialize the database semi-idempotently on every connection.

Docker-DCO-1.1-Signed-off-by: Erik Hollensbe <github@hollensbe.org> (github: erikh)
Talk about URL support and the real meaning of `-` in the latest `fromSrc` API documentation.

Signed-off-by: Jean-Paul Calderone <exarkun@twistedmatrix.com>
Update the most recent released version of the docs as well.

Signed-off-by: Jean-Paul Calderone <exarkun@twistedmatrix.com>
Merge pull request #9089 from cpuguy83/8942_create_volumes_on_create

Initialize volumes when container is created
Fix tests with old cmd function.

Docker-DCO-1.1-Signed-off-by: Jessica Frazelle <jess@docker.com> (github: jfrazelle)
Merge pull request #9490 from jfrazelle/fix-test-cmd-eff

Fix tests with old cmd function.
Merge pull request #9451 from erikh/fix-sqlite

graphdb: initialize the database semi-idempotently on every connection, not just new installs.
Merge pull request #9486 from ClusterHQ/9484-fromSrc-api-docs

Document fromSrc more clearly
Something changed, broke the docs release script, and it seems that --exclude still doesn't work, so I'm removing it

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
Merge pull request #9495 from SvenDowideit/aws-cli-exclude-still-broken

Something changed, broke the docs release script, and it seems that --ex...