s3fs: unable to access MOUNTPOINT error about docker-s3fs-client HOT 5 CLOSED

I played around with the S3S_ARGS, and could make it work with the option: use_path_request_style

Agree, struggled my butt off until I found this thread, and had to add env

  - S3FS_ARGS=use_path_request_style

from docker-s3fs-client.

I played around with the S3S_ARGS, and could make it work with the option: use_path_request_style

from docker-s3fs-client.

Try removing the -o from the S3FS_ARGS and see if it works better.

from docker-s3fs-client.

i have the same error, without the S3FS_ARGS, it gives me this output:

Mounting bucket test1 onto /opt/s3fs/bucket, owner: 0:0
FUSE library version: 2.9.9
nullpath_ok: 0
nopath: 0
utime_omit_ok: 1
unique: 2, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.32
flags=0x03fffffb
max_readahead=0x00020000
   INIT: 7.19
   flags=0x00000011
   max_readahead=0x00020000
   max_write=0x00020000
   max_background=0
   congestion_threshold=0
   unique: 2, success, outsize: 40

but the bucket never gets mounted to the local directory.

When using the s3fs mount command from the OS, it works somehow...

from docker-s3fs-client.

Closing as the README points to how to provide extra options to s3fs

from docker-s3fs-client.