WithBindMount issues with file permissions and mapping cross OS

[davidfowl]

There are several issues with WithBindMount that have been filed by users resulting in 2 themes:

1. When there's a mismatch between the container and the host user, the container may have insufficient permissions to access to file (we've worked around this before Set read permissions to allow pgadmin container to read the generated config file #4191)
2. When the host for the docker container isn't the same as the machine calling WithBindMount, paths don't get mapped directly.

I ran into this while trying to run our tests on github actions. Certain containers when using a bind mount need to set the permissions to make it accessible.

We should look into fixing these issues.

[dbreshears]

Moving to the backlog as we need to discuss options and scope is a bit large for 9.1.

[lvde0]

I noticed that WithBindMount() manually roots the path (via Path.GetFullPath()) which causes permission issues in docker compose:

It generates:

    volumes:
      - type: "bind"
        target: "/app/cert.crt"
        source: "C:\\Repos\\aspire-test\\certs\\cert.crt"
        read_only: false

But the container (dotnet/nightly/yarp:2.3.0-preview.4) fails to read it. When I manually tweak the compose file and set source as a relative path (../certs/cert.crt) it works just fine.

OS: Windows 11

[RaspeR87]

I noticed that WithBindMount() manually roots the path (via Path.GetFullPath()) which causes permission issues in docker compose:

It generates:

volumes:
  - type: "bind"
    target: "/app/cert.crt"
    source: "C:\\Repos\\aspire-test\\certs\\cert.crt"
    read_only: false

But the container (dotnet/nightly/yarp:2.3.0-preview.4) fails to read it. When I manually tweak the compose file and set source as a relative path (../certs/cert.crt) it works just fine.

OS: Windows 11

Same for me...any workaround?