docker compose volume mounts not work on Windows #4303

jleetutorial · 2017-01-07T01:13:40Z

When running docker-compose up, we get this error:

ERROR: for dockerapp  Cannot create container for service dockerapp: Invalid bind mount spec "C:\\Users\\nidal\\dockerapp\\app:/app:rw": Invalid volume specification: 'C:\Users\nidal\dockerapp\app:/app:rw'
�[31mERROR�[0m: Encountered errors while bringing up the project.

The docker-compose file is attached below

version: '2'
services:
  dockerapp:
    build: .
    ports:
      - "5000:5000"
    volumes:
      - ./app:/app

  redis:
    image: redis:3.2.0

We get the error both on Docker for Windows and Docker toolbox running on Windows.

$ docker version
Client:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 06:14:34 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 06:14:34 2016
 OS/Arch:      linux/amd64

$ docker-compose version
docker-compose version 1.9.0, build 2585387
docker-py version: 1.10.6
CPython version: 2.7.12
OpenSSL version: OpenSSL 1.0.2h  3 May 2016

$docker-compose --verbose config
compose.config.config.find: Using configuration files: .\docker-compose.yml
networks: {}
services:
  dockerapp:
    build:
      context: C:\Users\nidal\dockerapp
    ports:
    - 5000:5000
    volumes:
    - C:\Users\nidal\dockerapp\app:/app:rw
  redis:
    image: redis:3.2.0
version: '2.0'
volumes: {}

The text was updated successfully, but these errors were encountered:

shin- · 2017-01-07T01:21:21Z

Did you set COMPOSE_CONVERT_WINDOWS_PATHS ?

jleetutorial · 2017-01-25T19:52:46Z

We made a .env file in same directory as docker-compose.yml file

and added COMPOSE_CONVERT_WINDOWS_PATHS=1

we have also tried this to be true.

but still getting below error.

ABHISHEK@WindowsAbhi MINGW64 ~/Desktop/docker/dockerapp-releases/dockerapp-0.4/dockerapp-0.4
$ docker-compose up
dockerapp04_redis_1 is up-to-date
Creating dockerapp04_dockerapp_1

ERROR: for dockerapp Cannot create container for service dockerapp: Invalid bind mount spec "C:\Users\ABHISHEK\Desktop\docker\dockerapp-releases\dockerapp-0.4\do
ckerapp-0.4\app:/app:rw": Invalid volume specification: 'C:\Users\ABHISHEK\Desktop\docker\dockerapp-releases\dockerapp-0.4\dockerapp-0.4\app:/app:rw'
←[31mERROR←[0m: Encountered errors while bringing up the project.

abhisheks2010 · 2017-01-28T22:19:21Z

Is there a better way to do COMPOSE_CONVERT_WINDOWS_PATHS or any other workaround.

igordata · 2017-02-02T04:42:02Z

Just type "export COMPOSE_CONVERT_WINDOWS_PATHS=1" and it will work until reboot.

BlakeWills · 2017-06-02T14:22:25Z

Any reason this was closed? I've created a system environment variable and tried the .env file but still no avail.

shin- · 2017-06-02T16:40:50Z

It's not closed, but that particular issue should be resolved. Make sure your Compose version is up to date and your docker-compose.yml is correct.

DavidAdamczyk · 2017-06-10T09:54:32Z

I have the same issue on Windows 10. I use docker-compose version 1.11.2, build f963d76 and Docker version 17.03.1-ce, build c6d412e and this repo https://github.com/b00giZm/docker-compose-nodejs-examples/tree/master/00-basic-express-generator with correct Dockerfile and docker-compose.yml when i run docker-inspect i get this info: https://www.pastiebin.com/593bc096af354 but when i go inside to container and run ls /src i get this:

root@930bfd8a7df0:/src# ls
node_modules  package.json

i can't find app directory inside container.
But when i run:

PS D:\00-basic-express-generator> docker run --rm -v c:/Users:/data alpine ls /data
Administrator
All Users
Default
Default User

volumes is working great

Is there any solution how to fix this bug in docker-compose?

HWiese1980 · 2017-07-15T15:30:38Z

One and a half months... is there a solution yet?

rolandwolters · 2017-07-17T08:52:05Z

Running Docker 17.06.0-ce-win19 (12801) on Windows 10 using Visual Studio 2017 I ran into this thing.
I saw the "create e .env file" tip but on Window you cannot have a file with no name?

HWiese1980 · 2017-07-17T11:12:30Z

Yes, you can. At least on Windows 10.

riker09 · 2017-07-25T14:27:47Z

@rolandwolters You cannot have a file without a filename in Explorer. But you can open a Powershell, navigate to your project directory and type:

mv e.env .env

shin- · 2017-07-25T23:58:49Z

If you're still having issues, please make sure your shared drives are configured properly: https://blogs.msdn.microsoft.com/stevelasker/2016/06/14/configuring-docker-for-windows-volumes/

cre8 · 2017-08-15T14:12:58Z

It worked for me with COMPOSE_CONVERT_WINDOWS_PATHS=1, but I had to shut down all containers docker-compose stop, not just the one who uses it.

peteanusergiu · 2017-09-10T08:52:53Z

I've used , in a CMD window, SET COMPOSE_CONVERT_WINDOWS_PATHS=1 and it suddenly starting working. Remember to open a new CMD window.

jaspervandaele · 2017-11-14T16:50:06Z

I just discovered the "Reset Credentials..." button in the Shared Drive settings, which solved the issue for me. In my case the volume suddenly stopped working after disabling+enabling Hyper-V. Resetting the credentials for the shared drives fixed it again

cvillerm · 2017-11-15T15:05:17Z

@jaspervandaele, thanks a lot, this fixed my issue too. The error message Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type I was facing was so generic that I was wondering what was wrong. As I changed my Windows credentials recently, this is what caused this error. I wished there was something more explicit in case the mounted volume cannot be accessed at all

brianrichins · 2017-12-07T18:10:41Z

@rolandwolters You can bypass the Windows Explorer naming restriction by adding an extra . at the end. So renaming a file and typing ".env." results in .env, ".gitignore." becomes .gitignore, etc.

aysark · 2018-03-14T18:55:23Z

@jaspervandaele thanks for that- solved it for me.

gersondinis · 2018-04-08T16:31:14Z

On Command Line: "set COMPOSE_CONVERT_WINDOWS_PATHS=1";
Restart Docker for Windows;
Go to Docker for Windows settings > Shared Drives > Reset credentials > select drive > Apply;
Reopen Command Line;
Kill the Containers;
Rerun the Containers.

wsmelton · 2018-04-24T11:43:57Z

@gersondinis there is no option in settings for Shared Drives when Docker CE is running in Windows mode...unless I'm missing something using edge release:

gersondinis · 2018-04-24T15:20:52Z

Try to change from edge version to stable version on Daemon tab.
You should see something like this:
https://cdn-enterprise.discourse.org/docker/uploads/default/optimized/2X/d/df575b41215fb89a1f79f6bf8f0864b7366e9955_1_690x312.png

If it doesn't, try to upgrade/update your Docker for Windows.

tnovau · 2018-04-30T12:31:31Z

@gersondinis Thanks!, that solved my problem!

wsmelton · 2018-05-10T03:15:00Z

@gersondinis latest version of CE and stable version...this is all I get:

roeehershko · 2018-05-23T15:40:27Z

@gersondinis Sir your a life saver!
for me it wasnt the environment variable, it was due to changing windows password, thanks you sir!

dbjpanda · 2018-11-27T13:02:51Z

Will $PWD also work with COMPOSE_CONVERT_WINDOWS_PATHS=1 ? e.g

drupal:
    driver: local
    driver_opts:
      type: none
      device: $PWD/code/drupal
      o: bind

aalkz · 2018-12-13T08:17:07Z

I was having this issue (at least I think it's the same issue), but since I wanted to keep Hyper-V off in order to use accelerated emulation for Intel + Android, I couldn't use the Docker for Windows GUI app and look for those Shared Drives settings that @shin- mentioned, because I was using docker-machine.exe + VirtualBox. So what I had to do in this particular case instead was this: https://forums.docker.com/t/how-to-share-volumes-and-or-drives-using-docker-machine-on-windows-not-beta/20170/2

& "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" sharedfolder add default --name "shared" --hostpath "C:/your/shared/folder/" --automount

And then in docker-compose.yml:

volumes:
      - /shared:/some/dir/in/the/container

I think this is more like a workaround and not a full solution, but I hope somebody finds it helpful.

TL;DR: If you're using VirtualBox and not Docker for Windows, try mounting the drives in VirtualBox with VBoxManage.exe

BenMatheja · 2019-02-03T09:02:02Z

I'm using windows subsystem for linux, running the docker-host on the windows machine exposed via non-TLS port 2375.

I tried what @stavrogin mentioned, but it did not work.
My docker-compose.yml mounts a file into the container like this:

version: '2'

services:
  nginx:
    image: nginx:latest
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
    ports:
      - 80:80
      - 443:443

After running docker-compose up i get " Are you trying to mount a directory onto a file (or vice-versa)"

Starting ea_nginx_1 ...
Starting ea_grafana_1 ...
Starting ea_influxdb_1 ...
Starting ea_collectd_1 ... error

ERROR: for ea_collectd_1  Cannot start service collectd: b'OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: containeStarting ea_nginx_1    ... error947aaf139ee40bd985d078112919c30/merged\\\\\\" at \\\\\\"/var/lib/docker/overlay2/7a737fdd9749373317586ea8c17258c8b947aaf139ee40bd985d078112919c30/merged/etc/collectd/collectd.conf\\\\\\" caused \\\\\\"not a directory\\\\\\"\\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is
the expected type'

ERROR: for ea_nginx_1  Cannot start service nginx: b'OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \\"rootfs_linux.go:58: mounting \\\\\\"/mnt/d/Daten/workspace/ea/nginx.conf\\\\\\" to rootfs \\\\\\"/var/lib/docker/overlay2/db2c014e375524c7b6bf97cc874915d023c25b8e8f

I tried placing an .env file within the directory

 ben@ben-desktop  /d/Daten/workspace/ea   master ●  ls -al
total 60
drwxrwxrwx 1 ben ben  4096 Feb  3 09:47 .
drwxrwxrwx 1 ben ben  4096 Feb  3 08:44 ..
-rwxrwxrwx 1 ben ben 34197 Feb  3 08:37 collectd.conf
-rwxrwxrwx 1 ben ben   765 Feb  3 09:32 docker-compose.yml
-rwxrwxrwx 1 ben ben    31 Feb  3 09:52 .env
drwxrwxrwx 1 ben ben  4096 Feb  3 10:03 .git
-rwxrwxrwx 1 ben ben  2641 Feb  3 08:37 influxdb.conf
-rwxrwxrwx 1 ben ben  1086 Feb  3 08:37 LICENSE
-rwxrwxrwx 1 ben ben   169 Feb  3 09:26 nginx.conf
-rwxrwxrwx 1 ben ben   629 Feb  3 08:37 README.md
-rwxrwxrwx 1 ben ben  8577 Feb  3 08:37 types.db
 ben@ben-desktop  /d/Daten/workspace/ea   master ● 

But still cannot start the containers from my Windows machine. Running the exact same configuration on a linode works as is. What am I missing out here?

Edit: Moving the repository within the subsystem /home/ben/ea did also not resolve it

Edit: I fixed it with changing the Volumes from

 nginx:
    image: nginx:latest
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
    ports:
      - 80:80
      - 443:443

to

 nginx:
    image: nginx:latest
    volumes:
      - ${PWD}/nginx.conf:/etc/nginx/nginx.conf
    ports:
      - 80:80
      - 443:443

gischy · 2019-02-18T16:12:24Z

using docker toolbox on windows this way i could solve my the issue
https://medium.com/@Charles_Stover/fixing-volumes-in-docker-toolbox-4ad5ace0e572

docker-compose.yml:

version: '3'
services:
web:
build: .
ports:
- "5000:5000"
volumes:
- //c/var/docker-compose-test:/code
redis:
image: "redis:alpine"

- With long-running hosts, rooting the volumes inside of the git cloned source directory is problematic. When tests are cancelled and containers remain running, files can be locked, preventing subsequent runs from proceeding correctly. Instead, generate a temporary directory in Azure to root the files so that source can be cloned properly. - This removes the need for cleaning up existing hardcoded dirs in Azure from prior test runs - For now this will continue to default to `.` in Travis, given hosts are ephemeral - Additional code will be added to perform cleanup from tests - The Azure specific PowerShell code converts a Windows path like: c:\foo\bar\tmp.foo To something compose understands like: //c/foo/bar/tmp.foo See docker/compose#4303 (comment)

- With long-running hosts, rooting the volumes inside of the git cloned source directory is problematic. When tests are cancelled and containers remain running, files can be locked, preventing subsequent runs from proceeding correctly. Instead, generate a temporary directory (on Windows) to root the files so that source can be cloned properly. - This removes the need for cleaning up existing hardcoded dirs from prior test runs, but we still make a best effort in the Azure job to do cleanup - For now this will continue to default to `.` in Travis, given hosts are ephemeral. On Windows hosts, this will be in the temp dir for the given user. docker-compose understands Windows paths on the left hand side of the volume mapping, so no conversions are necessary. This was not always the case per: docker/compose#4303 (comment) - Stuff the temp dir in an Azure variable so it can be used in a later cleanup stage - Set the temp dir to give Users group full control to prevent the containers from running into permissions issues - Additional code will be added to perform cleanup from tests

saulonunesdev · 2020-02-25T09:10:00Z

If you're still having issues, please make sure your shared drives are configured properly: https://blogs.msdn.microsoft.com/stevelasker/2016/06/14/configuring-docker-for-windows-volumes/

and this COMPOSE_CONVERT_WINDOWS_PATHS=1

Worked for me

vkim-rogers · 2020-03-28T10:23:35Z

This settings in the docker-compose file work well:

    volumes:
      - type: bind
        source: ./source_local_directory
        target: c:\target_directory
        bind:
          propagation: cached

Thank you, it is working.

BTW, please keep in mind you should use at least version 3.3 of docker-compose YAML notation.

systemsincode · 2020-03-29T12:29:36Z

This settings in the docker-compose file work well:

    volumes:
      - type: bind
        source: ./source_local_directory
        target: c:\target_directory
        bind:
          propagation: cached

This fixed it for me too...

datocrats-org · 2020-05-28T09:52:13Z

What about ownership between windows docker host and container users, assuming docker-compose volume mounts correctly, the drivers do not seem to exist to translate ownership. Would we need to chown after each docker-compose up if we wanted to edit the mounted data on windows, for example?

prasannjeet · 2020-09-12T15:49:58Z

I just discovered the "Reset Credentials..." button in the Shared Drive settings, which solved the issue for me. In my case the volume suddenly stopped working after disabling+enabling Hyper-V. Resetting the credentials for the shared drives fixed it again

Can someone elaborate this please? I don't understand where can I find these settings.

danielleiszen · 2020-10-02T23:17:26Z

I just discovered the "Reset Credentials..." button in the Shared Drive settings, which solved the issue for me. In my case the volume suddenly stopped working after disabling+enabling Hyper-V. Resetting the credentials for the shared drives fixed it again

Can someone elaborate this please? I don't understand where can I find these settings.

On the latest Docker for Windows GUI these settings are removed, I guess because this version is not supposed to loose credentials

- With long-running hosts, rooting the volumes inside of the git cloned source directory is problematic. When tests are cancelled and containers remain running, files can be locked, preventing subsequent runs from proceeding correctly. Instead, generate a temporary directory (on Windows) to root the files so that source can be cloned properly. - This removes the need for cleaning up existing hardcoded dirs from prior test runs, but we still make a best effort in the Azure job to do cleanup - For now this will continue to default to `.` in Travis, given hosts are ephemeral. On Windows hosts, this will be in the temp dir for the given user. docker-compose understands Windows paths on the left hand side of the volume mapping, so no conversions are necessary. This was not always the case per: docker/compose#4303 (comment) - Stuff the temp dir in an Azure variable so it can be used in a later cleanup stage - Set the temp dir to give Users group full control to prevent the containers from running into permissions issues - Additional code will be added to perform cleanup from tests

shin- added area/volumes group/windows-client labels Jan 7, 2017

mercuriete mentioned this issue Feb 13, 2017

mount /var/lib/docker is not working on docker-toolbox mercuriete/docker-logstash-fluentd-elastic-kibana#2

Closed

shin- closed this as completed Jul 25, 2017

teohhanhui mentioned this issue Apr 11, 2018

Cannot start docker services api-platform/api-platform#575

Closed

FlorentTorregrosa mentioned this issue May 31, 2018

Installation projet : erreur avec docker-compose up Drupal-FR/site-drupalfr#66

Closed

ciccio14 mentioned this issue Nov 21, 2018

errore su docker italia/spid-testenv#2

Open

michaljelonek mentioned this issue Jan 23, 2019

docker-compose up gives this error - ModuleNotFoundError: No module named 'saleor' saleor/saleor#3465

Closed

xav-b mentioned this issue Feb 4, 2019

Error wile building with docker-compose backstopmedia/kong-book-example#2

Open

keulinho mentioned this issue Jun 12, 2019

Docker Installation on Windows shopware/development#28

Closed

gabimelo mentioned this issue Oct 9, 2019

not working on windows gabimelo/flask-boilerplate#3

Open

dongweiming mentioned this issue Nov 10, 2019

win10 subsystem can't docker-compose up dongweiming/lyanna#40

Closed

ArRomanov mentioned this issue Dec 22, 2019

Не запускается docker-compose supremko/docker#1

Closed

This was referenced Apr 19, 2020

Windows Problem with Docker Volume of Postgres CodingGarden/inventory-app#2

Closed

[Docker] Volumes within db causes issue's on Windows CodingGarden/inventory-app#1

Open

JoaoSant0s mentioned this issue May 3, 2020

Problemas de instalação no Windows cuducos/fio-de-ariadne#26

Open

jspaaks mentioned this issue Oct 15, 2020

add setting for building docker on windows research-software-directory/research-software-directory#522

Merged

pashidlos mentioned this issue Mar 13, 2021

Backup Data associated with a particular Api Key Visual-Regression-Tracker/Visual-Regression-Tracker#184

Closed

zhiltsov-max mentioned this issue Oct 10, 2022

Unable to run rest api tests - No such container:path: test_cvat_server_1:\tmp cvat-ai/cvat#5063

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docker compose volume mounts not work on Windows #4303

docker compose volume mounts not work on Windows #4303

jleetutorial commented Jan 7, 2017 •

edited

Loading

shin- commented Jan 7, 2017

jleetutorial commented Jan 25, 2017 •

edited

Loading

abhisheks2010 commented Jan 28, 2017

igordata commented Feb 2, 2017

BlakeWills commented Jun 2, 2017

shin- commented Jun 2, 2017

DavidAdamczyk commented Jun 10, 2017

HWiese1980 commented Jul 15, 2017

rolandwolters commented Jul 17, 2017

HWiese1980 commented Jul 17, 2017

riker09 commented Jul 25, 2017

shin- commented Jul 25, 2017

cre8 commented Aug 15, 2017

peteanusergiu commented Sep 10, 2017

jaspervandaele commented Nov 14, 2017

cvillerm commented Nov 15, 2017

brianrichins commented Dec 7, 2017 •

edited

Loading

aysark commented Mar 14, 2018

gersondinis commented Apr 8, 2018

wsmelton commented Apr 24, 2018

gersondinis commented Apr 24, 2018 •

edited

Loading

tnovau commented Apr 30, 2018

wsmelton commented May 10, 2018

roeehershko commented May 23, 2018

dbjpanda commented Nov 27, 2018

aalkz commented Dec 13, 2018

BenMatheja commented Feb 3, 2019 •

edited

Loading

gischy commented Feb 18, 2019

saulonunesdev commented Feb 25, 2020

vkim-rogers commented Mar 28, 2020

systemsincode commented Mar 29, 2020

datocrats-org commented May 28, 2020

prasannjeet commented Sep 12, 2020

danielleiszen commented Oct 2, 2020

docker compose volume mounts not work on Windows #4303

docker compose volume mounts not work on Windows #4303

Comments

jleetutorial commented Jan 7, 2017 • edited Loading

shin- commented Jan 7, 2017

jleetutorial commented Jan 25, 2017 • edited Loading

abhisheks2010 commented Jan 28, 2017

igordata commented Feb 2, 2017

BlakeWills commented Jun 2, 2017

shin- commented Jun 2, 2017

DavidAdamczyk commented Jun 10, 2017

HWiese1980 commented Jul 15, 2017

rolandwolters commented Jul 17, 2017

HWiese1980 commented Jul 17, 2017

riker09 commented Jul 25, 2017

shin- commented Jul 25, 2017

cre8 commented Aug 15, 2017

peteanusergiu commented Sep 10, 2017

jaspervandaele commented Nov 14, 2017

cvillerm commented Nov 15, 2017

brianrichins commented Dec 7, 2017 • edited Loading

aysark commented Mar 14, 2018

gersondinis commented Apr 8, 2018

wsmelton commented Apr 24, 2018

gersondinis commented Apr 24, 2018 • edited Loading

tnovau commented Apr 30, 2018

wsmelton commented May 10, 2018

roeehershko commented May 23, 2018

dbjpanda commented Nov 27, 2018

aalkz commented Dec 13, 2018

BenMatheja commented Feb 3, 2019 • edited Loading

gischy commented Feb 18, 2019

saulonunesdev commented Feb 25, 2020

vkim-rogers commented Mar 28, 2020

systemsincode commented Mar 29, 2020

datocrats-org commented May 28, 2020

prasannjeet commented Sep 12, 2020

danielleiszen commented Oct 2, 2020

jleetutorial commented Jan 7, 2017 •

edited

Loading

jleetutorial commented Jan 25, 2017 •

edited

Loading

brianrichins commented Dec 7, 2017 •

edited

Loading

gersondinis commented Apr 24, 2018 •

edited

Loading

BenMatheja commented Feb 3, 2019 •

edited

Loading