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
I've tried your container with latest version of s3fs running on 1.89.
When I try to setup the container using a MinIO backend endpoint, I run into the following error:
s3fs: Unable to access MOUNTPOINT my-bucket: No such file or directory
Mount failure
I guess your startup script created the directory /opt/s3fs/bucket but not the directory which actually holds the bucket, which would need to be opt/s3fs/bucket/my-bucket if I understand correctly.
Thus, you'd have to change the entrypoint script to mkdir -p $DEST/$AWS_S3_BUCKET or something like that.
I used ACCESS_KEY/SECRET_KEY combination instead of a keyfile and added S3FS_ARGS: "use_path_request_style,allow_other,default_acl=public".
Do you have any other hints on this?
The text was updated successfully, but these errors were encountered:
Greetings,
I've tried your container with latest version of
s3fs
running on1.89
.When I try to setup the container using a MinIO backend endpoint, I run into the following error:
I guess your startup script created the directory
/opt/s3fs/bucket
but not the directory which actually holds the bucket, which would need to beopt/s3fs/bucket/my-bucket
if I understand correctly.Thus, you'd have to change the entrypoint script to
mkdir -p $DEST/$AWS_S3_BUCKET
or something like that.I used
ACCESS_KEY
/SECRET_KEY
combination instead of a keyfile and addedS3FS_ARGS: "use_path_request_style,allow_other,default_acl=public"
.Do you have any other hints on this?
The text was updated successfully, but these errors were encountered: