mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #653] Cannot mount a bucket that has a dot(.) in its name even though I use "use_path_request_style" #370
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#370
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MariusStanciu95 on GitHub (Oct 3, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/653
I'm using 1.82 or newer and I keep getting unknown option "use_path_request_style" or "endpoint".
I've read that if my bucket has a dot(.) inside its name , I should use the "use_path_request_style" option.
My call when I try mounting:
s3fs bucket.name /mnt/s3 -o passwd_file=/etc/passwd-s3fs -endpoint=eu-west-2 -o use_path_request_style
Did anyone encounter this problem? Any suggestions (besides renaming the bucket, because I'm not allowed to do that) ?
@gaul commented on GitHub (Oct 3, 2017):
Please post the logs from the failed command.
@djdevin commented on GitHub (Nov 6, 2017):
I posted logs in #626
@Vacilando commented on GitHub (Nov 9, 2017):
Same problem here. If the bucket name contains a dot, s3fs mount fails (no error message).
@stevesuh commented on GitHub (Dec 6, 2017):
Same here. This worked back in August.
@ggtakec commented on GitHub (Mar 29, 2019):
We kept this issue open for a long time.
Please try again with the latest version and you can see https://github.com/s3fs-fuse/s3fs-fuse/wiki/FAQ#q-https-connecting-failed-if-bucket-name-includes-dot- .
I will close this, but if the problem persists, please reopen or post a new issue.