Docker Community Forums

Share and learn in the Docker community.

Incorrect drive mounted in volume

docker

(Gsparx) #1

Issue type: defect

I have an issue with a secondary hard drive not mounting properly. I have two drives in my machine, an SSD which is my C:/ drive, and an HDD which is my E:/ drive.

I have both drives shared via the docker application. I have tried this with both shared, and with only the E:/ drive shared.

when I run docker run --rm -v e:/:/data alpine ls /data, I have noticed that I get the exact same result as running docker run --rm -v c:/:/data alpine ls /data. Basically, trying to ls in the E drive is giving me the result of running ls in the C drive.

OS Version/build

Client:
 Version:       17.12.0-ce
 API version:   1.35
 Go version:    go1.9.2
 Git commit:    c97c6d6
 Built: Wed Dec 27 20:05:22 2017
 OS/Arch:       windows/amd64

Server:
 Engine:
  Version:      17.12.0-ce
  API version:  1.35 (minimum version 1.12)
  Go version:   go1.9.2
  Git commit:   c97c6d6
  Built:        Wed Dec 27 20:12:29 2017
  OS/Arch:      linux/amd64
  Experimental: true

Windows 10 Pro 1709 : 16299.248

Steps to reproduce

  1. Install and launch docker for windows
  2. Have E: and C: drives (E is not a network drive, just a secondary hard drive)
  3. run docker run --rm -v e:/:/data alpine ls /data
  4. expected behavior: contents of E:/ is listed
  5. actual behavior: contents of C:/ is listed

Thanks for any help with this!


(Sam) #2

use the mount syntax… the : (colon character) is the source/dest separate in the -v syntax

--mount,type=bind,source=c:\,dest=/data

or use the cygwin type syntax

-v /c/:/data