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>
refer to the registry instead of the hub

Signed-off-by: Jeff Anderson <jeff@docker.com>
Fix dead link in oracle.md
Fix dead link cli.md
Check for no `Cmd` on exec create endpoint

Fixes #9414

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
Try other port on any error from Map

Sometimes other programs can bind on ports from our range, so we just
skip this ports on allocation.

Fixes #9293
Probably fixes #8714

Signed-off-by: Alexander Morozov <lk4d4@docker.com>
Fix client-side HTTP hijacking over TLS

Properly CloseWrite() the client socket once done with stdin when using
TLS connection (this used to rely on an erroneous type assertion).

Fixes #8658.
Fixes #8642.

Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>
Signed-off-by: Michael Crosby <crosby.michael@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>
graphdb: initialize the database semi-idempotently on every connection.

Docker-DCO-1.1-Signed-off-by: Erik Hollensbe <github@hollensbe.org> (github: erikh)
Merge pull request #9442 from icecrime/8658-tls_attach_hangs

Fix client-side HTTP hijacking over TLS
Update dockerimages.md

remove 'public registry'

Signed-off-by: Jeff Anderson <jeff@docker.com>
Merge pull request #9441 from LK4D4/retry_any_error_on_portmap

Try other port on any error from Map
Merge pull request #9435 from cpuguy83/9414_fix_exec_api_error_no_cmd

Check for no `Cmd` on exec create endpoint
Remove unused Engine.Logf

The `Engine.Logf` method was unused and confusing.

Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>
Merge pull request #9457 from icecrime/engine_logf

Remove unused Engine.Logf method
Webhooks documentation: second pass addressing @fredlf's comments

Signed-off-by: Joffrey F <joffrey@docker.com>
Merge pull request #9273 from programmerq/dockerimages_hub

refer to the registry instead of the hub
Merge pull request #9460 from shin-/docs_webhooks2

Webhooks documentation: additional improvements
Fix TarSum iteration test

I noticed that 3 of the tarsum test cases had expected a tarsum with
a sha256 hash of
  e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
As I've been working with sha256 quite a bit lately, it struck me that
this is the initial digest value for sha256, which means that no data
was processed. However, these tests *do* process data. It turns out that
there was a bug in the test handling code which did not wait for tarsum
to end completely. This patch corrects these test cases.

I'm unaware of anywhere else in the code base where this would be an issue,
though we definitily need to look out in the future to ensure we are
completing tarsum reads (waiting for EOF).

Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn)
Merge pull request #9463 from jlhawn/tarsum_test_fix

Fix TarSum iteration test