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>
Rename overlayfs to overlay

Since Linux 3.18-rc6, overlayfs has been renamed overlay.

This change was introduced by the following commit in linux.git:
ef94b1864d1ed5be54376404bb23d22ed0481feb ovl: rename filesystem type to "overlay"

Signed-off-by: Lénaïc Huard <lhuard@amadeus.com>
Rename the overlay storage driver

so that docker is started with `docker -d -s overlay` instead of `docker -d -s overlayfs`

Signed-off-by: Lénaïc Huard <lhuard@amadeus.com>
Remove the last references to overlayfs

This only renames docker internal structures.
It has no impact on the end-user.

Signed-off-by: Lénaïc Huard <lhuard@amadeus.com>
Merge pull request #9426 from lhuard1A/overlay_rename

Rename overlayfs to overlay
Fix invalid argument error on push

With 32ba6ab from #9261, TempArchive now closes the underlying file and
cleans it up as soon as the file's contents have been read. When pushing
an image, PushImageLayerRegistry attempts to call Close() on the layer,
which is a TempArchive that has already been closed. In this situation,
Close() returns an "invalid argument" error.

Add a Close method to TempArchive that does a no-op if the underlying
file has already been closed.

Signed-off-by: Andy Goldstein <agoldste@redhat.com>
Merge pull request #9482 from ncdc/TempArchive-close-bug

Fix invalid argument error on push
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.
Added description for 'docker run' command, -c/--cpu-shares flag

Signed-off-by: Shishir Mahajan <shishir.mahajan@redhat.com>
Docker run command with -c/--cpu-shares=0 will reflect container JSON 'CpuShares' as 1024, in sync with the file system value

Signed-off-by: Shishir Mahajan <shishir.mahajan@redhat.com>