Wrong resolving of relative volume paths

[chrfranz]

Relative paths in the docker-compose.yml are not resolved correctly. This is because the working directory inside the container defaults to /compose.

Given the following directory structure:

docker-compose.yml
|-folder
    |-myfile.txt

And the following docker-compose.yml file:

services:
  myservice:
    volumes:
       - ./folder/myfile.txt:/etc/folder/myfile.txt

Running docker-compose will result in an error:

OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/compose/folder/myfile.txt" to rootfs at "/etc/folder/myfile.txt"

According the docker-compose specification the . should be resolved to the directory where the docker-compose.yml is located and not to the /compose directory.

[DirkMeihoefer]

You have to start the container in the folder where the docker-compose.yml is located.
This way the mount "-v $(pwd):/compose" is correctly resolved.