Non-executable files mounted via gRPC FUSE have execute access

[cknave]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: D9BD25FE-12BF-4841-A516-2FCF3B2368E6/20201019154923

Expected behavior

Given a file mounted via gRPC FUSE with the execute bits UNSET, access("/some/file", X_OK) returns an access denied error

Actual behavior

access() returns success

Information

• macOS Version: 10.15.7
• docker desktop 2.4.0.0
• downgrading to docker desktop 2.3.0.5 or disabling gRPC FUSE returns the expected behavior

Diagnostic logs

Diagnose succeeded

Steps to reproduce the behavior

• simple test case: https://github.com/cknave/local-files-are-executable
• docker-compose run test

[stephen-turner]

@djs55 Comments?

[docker-robott]

Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[thierrymarianne]

Hello! We've reproduced this issue, which affected one of our development environment.

@tgachet and I would be happy to share reproducible details
if you'd like to have additional ones even though it appears @cknave did all the necessary digging already ⛏️

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked