S3FS_ARGS syntax in README.md about docker-s3fs-client HOT 5 CLOSED

The code auto-injects the -o:

from docker-s3fs-client.

I didn't specified a version, so I assume I use the latest.

from docker-s3fs-client.

Here is my docker-compose.yml file :

---
version: '3.8'
services:
  s3fs:
    privileged: true
    image: efrecon/s3fs
    restart: unless-stopped
    environment:
      - AWS_S3_URL=${S3_ENDPOINT_URL}
      - AWS_S3_BUCKET=${S3_BUCKET_NAME}
      - AWS_S3_ACCESS_KEY_ID=${S3_ACCESS_KEY_ID}
      - AWS_S3_SECRET_ACCESS_KEY=${S3_SECRET_ACCESS_KEY}
      - UID=${S3_UID}
      - GID=${S3_GID}
      - S3FS_ARGS='-oallow_other'
      - S3FS_DEBUG=0
    volumes:
      - ${S3PATH}:/opt/s3fs/bucket:rshared
    devices:
      - /dev/fuse
    cap_add:
      - SYS_ADMIN
    security_opt:
      - apparmor=unconfined
# ...

When I change it to S3FS_ARGS='allow_other', I get :

s3fs_1 | s3fs: unable to access MOUNTPOINT xyzxyzxyzxyzxyzxyzxyzxyz: No such file or directory
s3fs_1 | Mount failure

Without that S3FS_ARGS option, mount succeed, but I have some "forbiden" access right problems in other docker services.

from docker-s3fs-client.

When I change it to S3FS_ARGS='allow_other', I get :

s3fs_1 | s3fs: unable to access MOUNTPOINT xyzxyzxyzxyzxyzxyzxyzxyz: No such file or directory
s3fs_1 | Mount failure

IIRC, I had the same error, removing the quotes should fix this: S3FS_ARGS=allow_other.

from docker-s3fs-client.

The quotes are misplaced according to the Docker compose specification (well, actually more of a YAML issue). If you want quotes, you should place them around the whole expression, i.e. "S3FS_ARGS=allow_other"

from docker-s3fs-client.