compose-go should resolve all relative paths about compose-go HOT 4 CLOSED

path starting by . MUST resolve from process working directory (os.Getwd)

I believe that for bind volumes defined in the service, the source path has to start with a ./, and it resolves relative to the compose file. E.g.

services:
  web:
    image: nginx
    volumes:
      - './foo:/bar'

from compose-go.

Good catch, docker-compose indeed resolves . based on compose file's parent folder, not working directory the command is ran from.
see https://github.com/docker/compose/blob/master/compose/config/config.py#L758-L759 where config_details.working_dir is set from compose file's parent folder (https://github.com/docker/compose/blob/master/compose/config/config.py#L304) or path set by --project-directory, not working directory the docker-compose command is ran from.

I'm updating this issue accordingly, thanks

from compose-go.

No problem -- very cool that you know the compose source so well! I just know bits and pieces through trial and error 😄

from compose-go.

both approaches are complimentary :)

from compose-go.