You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the latest tag, the UID and GID environment variables behave correctly: setting them allows only the specified user to access the mounted directory.
However, using any of the other recent tags, e.g. 1.91, 1.90, 1.89, etc., the UID and GID environment variables do nothing at all: the user whose UID and GID are specified will be granted access to the mounted directory only if the allow_other option is used. Otherwise, it gets a "permission denied" error.
BTW, which s3fs version is used in the latest tag?
The text was updated successfully, but these errors were encountered:
latest is hopelessly outdated (despite the name). But I think this is all because the version of latest was running s3fs as the user, which seems to have disappeared. I will have to dig in the commit history to understand why and when and return to you. The mount command should look like the following one:
Using the
latest
tag, theUID
andGID
environment variables behave correctly: setting them allows only the specified user to access the mounted directory.However, using any of the other recent tags, e.g.
1.91
,1.90
,1.89
, etc., theUID
andGID
environment variables do nothing at all: the user whose UID and GID are specified will be granted access to the mounted directory only if theallow_other
option is used. Otherwise, it gets a "permission denied" error.BTW, which
s3fs
version is used in thelatest
tag?The text was updated successfully, but these errors were encountered: