Startup option to ignore mode change errors

[pawalt]

Tell us more about this new feature.

We currently use mountpoint-s3 to allow our users to mount buckets in their containers as regular volumes. This has been working well, but there's one footgun that some of our users have run into - the mode changing errors. We have some users with pre-written scripts that automatically do a chmod on their files even if the mode is already properly set. For these users, mountpoint breaks their scripts as it throws errors on the chmod.

Would folks be open to a change to allow mountpoint to ignore change mode errors, effectively making them a no-op? This would be opt-in startup behavior, and it would make our lives much easier.

[dannycjones]

Hey @pawalt, thanks for opening this feature request. I'll bring this to the team, I can see why this could be useful.

[pawalt]

FYI we have implemented this on our fork:
modal-labs#3

[helenweng-stripe]

hey @dannycjones any updates on prioritizing this? It would be useful for us as well if we want to replace the Hadoop fs with s3 mountpoint.

[unexge]

Hey @helenweng-stripe, thanks for sharing your use-case. There is no update we can share as of now. I'd suggest adding thumps up reaction (👍) to the main comment to help us to track interest on this feature.