docker unexpectedly creates non-existent host volumes #16055
Description
This:
docker run -v /path/to/nonexistent/directory:/container-path ...
Results in docker creating /path/to/nonexistent/directory. I didn't expect this, and AFAICT, it's undocumented.
Linux mg-mesos 3.19.0-26-generic #28-Ubuntu SMP Tue Aug 11 14:16:32 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Client:
Version: 1.8.1
API version: 1.20
Go version: go1.4.2
Git commit: d12ea79
Built: Thu Aug 13 02:40:42 UTC 2015
OS/Arch: linux/amd64
Server:
Version: 1.8.1
API version: 1.20
Go version: go1.4.2
Git commit: d12ea79
Built: Thu Aug 13 02:40:42 UTC 2015
OS/Arch: linux/amd64
Containers: 30
Images: 112
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 172
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-26-generic
Operating System: Ubuntu 15.04
CPUs: 4
Total Memory: 11.62 GiB
Name: mg-mesos
ID: 7AES:SDZ5:WNYM:NM33:3FKF:SQK6:KYMM:DBXJ:DLGK:MN6L:WYRR:EFTI
Username: mgummelt
Registry: https://index.docker.io/v1/
WARNING: No swap limit support