Mounting relative volume from git stack

[sqrtroot]

Bug description
Portainer mounts the volume not based on absolute path of the host. But relative to container root?

Expected behavior
Mounting the relative path should be relative to the docker-compose.yaml file. It somehow mounts
/data/compose/13/Config/HomeAssistant on the host instead of /var/lib/docker/volumes/portainer_data/_data/compose/13/Config/HomeAssistant

Briefly describe what you were expecting.

Steps to reproduce the issue:

Steps to reproduce the behavior:

1. Create a stack with a relative mount in a git repo

version: "2"
services:
  home-assistant:
    image: homeassistant/home-assistant
    volumes:
      - ./Config/HomeAssistant:/config

2. Start the stack trough portainer
3. See a new folder on the host /data... and see that folder mounted instead of the correct folder

Technical details:

• Portainer version: Both latest and develop tag
• Docker version (managed by Portainer): Docker version 18.06.1-ce, build e68fc7a
• Platform (windows/linux): Linux 4.9.0-8-amd64 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 GNU/Linux
• Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):docker run --name portainer -d -p 80:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer:develop

Additional context
When deploying by nativly cloning and running docker-compose up this doesn't occur

[sqrtroot]

Output of docker inspect (interesting mount part)

"Mounts": [
            {
                "Type": "bind",
                "Source": "/data/compose/13/Config/HomeAssistant",
                "Destination": "/config",
                "Mode": "",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],

[sqrtroot]

Just tested this with alpine instead of home assistant. The issue still persists

[sqrtroot]

It also shows this behaviour when you don't use a git repo but just a plain docker-compose file from the text editor

[sqrtroot]

Any suggestions on where this problem could come from? I've read #1647 should fix that, but it doesn't look like it does.

[sqrtroot]

?

[simon-rohart]

Hello,
I also encounter this problem

[michelkaeser]

+1 I have the same expectations as OP

[stephenhouser]

+1 same problem and expectations as OP.

As a workaround (Linux host):

• Use local bind mount when running portainer (as in sample portainer-compose project) to /opt/portainer/data
• On host create a symlink from /data to /opt/portainer/data

[tomwiggers]

Hi,

This problem still persists. I understand it might be difficult to solve when pasting the contents of a compose-file in Portainer but shouldn't it be easier to fix when a repo is used? Clone the whole thing, then use paths relative to the compose file.

[ghost]

Closing as a duplicate of #2046