Problem with relative paths in volumes in Windows

[alexandrev]

I'm using the docker-compose version 1.5.0 with the pull-request #1957. When I'm trying to start a group of containers which one of them has a relative path in the volume section like this:

volumes:

• "./data:/var/run/docker.sock"

I'm getting this error:

b'invalid mode for volumes-from: /var/run/docker.sock'

[dnephin]

This error suggests it's using volumes_from not volumes, could you post your full docker-compose.yml ?

[alexandrev]

Of course. I've been trying different posiblities. This is the full one right now.

centosjava:
build: base
bw6agent:
build: bw6
links:

• "ambassador:tea"
  ports:
• "9091:9091"
• "5050:5050"
• "9090:9090"
• "8079:8079"
  hostname: bw6agent
  tea:
  build: tea
  links:
• "ambassador:bw6agent"
  ports:
• "8777:8777"
  hostname: tea
  ambassador:
  image: cpuguy83/docker-grand-ambassador
  volumes:
• "./data/docker.sock:/var/run/docker.sock"
  command: "-name tibcobw6_bw6agent_1 -name tibcobw6_tea_1"

[christianbundy]

@alexandrev You can use fenced code blocks with yaml syntax highlighting to format your code.

centosjava:
  build: base
bw6agent:
  build: bw6
  links:
    - "ambassador:tea"
  ports:
    - "9091:9091"
    - "5050:5050"
    - "9090:9090"
    - "8079:8079"
  hostname: bw6agent
tea:
  build: tea
  links:
    - "ambassador:bw6agent"
  ports:
    - "8777:8777"
  hostname: tea
ambassador:
  image: cpuguy83/docker-grand-ambassador
  volumes:
    - "./data/docker.sock:/var/run/docker.sock"
  command: "-name tibcobw6_bw6agent_1 -name tibcobw6_tea_1"

[alexandrev]

Thanks a lot @christianbundy and sorry for don't do it this way at first.

[msamblanet]

I am seeing a similar issue on a docker-compose up -d

connect:
  image: anvilresearch/connect:0.1.55
  links:
    - redis:redis
  volumes:
    - ./connect/config:/opt/connect/config:ro
    - ./connect/email:/opt/connect/email:ro
    - ./connect/protocols:/opt/connect/protocols:ro
    - ./connect/providers:/opt/connect/providers:ro
    - ./connect/public:/opt/connect/public:ro
    - ./connect/views:/opt/connect/views:ro
  restart: always

nginx:
  #build: nginx
  image: anvilresearch/nginx
  links:
    - connect:connect
  volumes:
    - ./nginx/conf.d:/etc/nginx/conf.d:ro
    - ./nginx/certs:/etc/nginx/certs:ro
    - ./nginx/logs:/var/log/nginx
  ports:
    - "80:80"
    - "443:443"
  restart: always

redis:
  image: anvilresearch/redis
  volumes:
    - ./redis/data:/data
  restart: always

Resulting error for me:

compose.service.ConfigError: Volume c:\Users\msamblanet\Documents\anvil\connect\config:/opt/connect/config:ro has incorrect format, should be external:internal[:mode]

I specifically installed using: pip install --upgrade git+https://github.com/aanand/fig.git@fb304981536722ef42c9688b0688d4be048ccfd1

That commit is (as of right now) the last commit on #1957

[ikb42]

@msamblanet me too

[msamblanet]

Pure FYI - tried to work around this by editing parse_volume_spec in service.py - I added the following code to detect and re-combine the drive and path after splitting on ":"

def parse_volume_spec(volume_config):
    parts = volume_config.split(':')

    # Deal with Windows formatted absolute paths - "c:\foo\bar\" - the : messes things up...
    if len(parts) == 4 and len(parts[0]) == 1 and parts[0].isalpha() and parts[1].startswith("\\"):
        parts[1] = parts[0] + ":" + parts[1]
        del parts[0]

    # Rest of function unmodified

This got past the current error BUT gave another error: Invalid volume specification: c:\Users\msamblanet\Documents\anvil\connect\views:\opt\connect\views:ro

I searched the python code for this message but did not find the relevant source for this new...

My tests are based around docker\compose on master now.

[mnowster]

Hi @msamblanet, thanks for the info. I have a PR waiting to get merged which should hopefully fix this. #2088

[msamblanet]

@mnowster - Thanks for the info on #2088 - I pulled a new version using:
pip install --upgrade git+https://github.com/mnowster/compose@6e505627ed3921bf85d818e216f97df84889cd56

And now I get this instead: Invalid volume specification: None:redis\data:\data:rw

Same docker-compose.yml as in my post above. I also replaced the relative path with an absolute path and got the same error.

On some attempts, not all, I got this warning:

Warning: the mapping "c:\Users\msamblanet\Documents\anvil\nginx\conf.d:/etc/nginx/conf.d:ro" in the volumes config for service "nginx" is ambiguous. In a future version of Docker, it will designate a "named" volume (see https://github.com/docker/docker/pull/14242). To prevent unexpected behaviour, change it to "./c:\Users\msamblanet\Documents\anvil\nginx\conf.d:/etc/nginx/conf.d:ro"