title: Docker-compose, remote context, path relative to local machine instead of remote
body: <p>I have a very simple docker-compose.yml:</p>
  <pre><code>version: '2.4'
  
  services:
    containername:
      image: ${DOCKER_IMAGE}
      volumes:
        - ./config:/root/config
  </code></pre>
  <p>I'm using a remote staging server accessed via ssh:</p>
  <pre><code>docker context create staging --docker &quot;host=ssh://ubuntu@staging.example.com&quot;
  docker context use staging
  </code></pre>
  <p>However, I see unexpected results with my volume after I <code>docker-compose up</code>:</p>
  <pre><code>docker-compose --context staging up -d
  docker inspect containername
  ...
          &quot;Mounts&quot;: [
              {
                  &quot;Type&quot;: &quot;bind&quot;,
                  &quot;Source&quot;: &quot;/Users/crummy/code/.../config&quot;,
                  &quot;Destination&quot;: &quot;/root/config&quot;,
                  &quot;Mode&quot;: &quot;rw&quot;,
                  &quot;RW&quot;: true,
                  &quot;Propagation&quot;: &quot;rprivate&quot;
              }
          ],
  ...
  </code></pre>
  <p>It seems the expansion of <code>./config</code> to a full path happens <em>on the machine docker-compose is running on</em>. Not the machine Docker is running on.</p>
  <p>I can fix this problem by hardcoding the entire path: <code>/home/ubuntu/config:/root/config</code>. But this makes my docker-compose file a little less flexible than it could be. Is there a way to get the dot expansion to occur on the remote machine?</p>