starred/s3fs-fuse

Fork 0

mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00

[GH-ISSUE #854] digital ocean spaces compatibility #497

New issue

Closed

opened 2026-03-04 01:46:07 +03:00 by kerem · 9 comments

kerem commented

2026-03-04 01:46:07 +03:00

Owner

Originally created by @pjebs on GitHub (Nov 8, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/854

Digital Ocean spaces claims to be S3 compatible in terms of their API and how it can be interfaced by external clients. Should s3fs work in theory?

Originally created by @pjebs on GitHub (Nov 8, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/854 Digital Ocean spaces claims to be S3 compatible in terms of their API and how it can be interfaced by external clients. Should s3fs work in theory?

kerem closed this issue

2026-03-04 01:46:07 +03:00

kerem commented

2026-03-04 01:46:08 +03:00

Author

Owner

@gaul commented on GitHub (Nov 8, 2018):

Yes it should. Please report back with your results.

@gaul commented on GitHub (Nov 8, 2018): Yes it should. Please report back with your results.

kerem commented

2026-03-04 01:46:08 +03:00

Author

Owner

@Niek commented on GitHub (Nov 14, 2018):

Yes, I'm using it with DO Spaces. Just specify: -o url=https://ams3.digitaloceanspaces.com/ or whatever your spaces endpoint is.

@Niek commented on GitHub (Nov 14, 2018): Yes, I'm using it with DO Spaces. Just specify: ``-o url=https://ams3.digitaloceanspaces.com/`` or whatever your spaces endpoint is.

kerem commented

2026-03-04 01:46:08 +03:00

Author

Owner

@nodje commented on GitHub (Nov 16, 2018):

I got a Spaces bucket mounted on a local folder on Macos, but I can only see the 3 main folder as zero-bytes document.
Here's what it looks like in a term:

----------    1 root  wheel     0 30 Oct 09:08 foldername

Dates are right though!

Is there anything specific I should do for s3fs to be able to retrieve/map object properties?

@nodje commented on GitHub (Nov 16, 2018): I got a Spaces bucket mounted on a local folder on Macos, but I can only see the 3 main folder as zero-bytes document. Here's what it looks like in a term: ``` ---------- 1 root wheel 0 30 Oct 09:08 foldername ``` Dates are right though! Is there anything specific I should do for s3fs to be able to retrieve/map object properties?

kerem commented

2026-03-04 01:46:08 +03:00

Author

Owner

@akyoto commented on GitHub (Dec 9, 2018):

I have the same problem as @nodje, can't access folders because they are 0-byte documents.

---------- 1 eduard eduard 0 Dec 8 17:46 documents

@akyoto commented on GitHub (Dec 9, 2018): I have the same problem as @nodje, can't access folders because they are 0-byte documents. `---------- 1 eduard eduard 0 Dec 8 17:46 documents`

kerem commented

2026-03-04 01:46:08 +03:00

Author

Owner

@Gandalf- commented on GitHub (Dec 23, 2018):

I was able to mount and access files on my SFO2 space with these options on Ubuntu 16.04.5 LTS and V1.79

I uploaded the files with s3cmd, and they all have private permissions.

s3fs bucket /mnt/bucket \
  -o passwd_file=$HOME/.passwd-s3fs \
  -o url=https://sfo2.digitaloceanspaces.com/ \
  -o uid=1000,gid=1000 \
  -o use_path_request_style

@Gandalf- commented on GitHub (Dec 23, 2018): I was able to mount and access files on my SFO2 space with these options on Ubuntu 16.04.5 LTS and V1.79 I uploaded the files with s3cmd, and they all have private permissions. ``` s3fs bucket /mnt/bucket \ -o passwd_file=$HOME/.passwd-s3fs \ -o url=https://sfo2.digitaloceanspaces.com/ \ -o uid=1000,gid=1000 \ -o use_path_request_style ```

kerem commented

2026-03-04 01:46:08 +03:00

Author

Owner

@gaul commented on GitHub (Feb 2, 2019):

@Gandalf- could you mount with -o umask=027 or try using master which provides a default when permissions do not exist?

@gaul commented on GitHub (Feb 2, 2019): @Gandalf- could you mount with `-o umask=027` or try using master which provides a default when permissions do not exist?

kerem commented

2026-03-04 01:46:08 +03:00

Author

Owner

@pjebs commented on GitHub (Feb 2, 2019):

@blitzprog The problem with s3 is that there are no such thing as folders. They 'artificially' pretend 0 byte files are folders.

@pjebs commented on GitHub (Feb 2, 2019): @blitzprog The problem with s3 is that there are no such thing as folders. They 'artificially' pretend 0 byte files are folders.

kerem commented

2026-03-04 01:46:09 +03:00

Author

Owner

@gaul commented on GitHub (Apr 9, 2019):

Please retest with 1.85 and reopen this issue if problems persist.

@gaul commented on GitHub (Apr 9, 2019): Please retest with 1.85 and reopen this issue if problems persist.

kerem commented

2026-03-04 01:46:09 +03:00

Author

Owner

@mike503 commented on GitHub (Jul 2, 2020):

still an issue in s3cmd 2.0.2. out of 4 "directories" in the root of my bucket, 3 of them are 0 byte "documents" and are unable to view them as a hierarchy. only one behaves like a directory.

@mike503 commented on GitHub (Jul 2, 2020): still an issue in s3cmd 2.0.2. out of 4 "directories" in the root of my bucket, 3 of them are 0 byte "documents" and are unable to view them as a hierarchy. only one behaves like a directory.