s3fs: unable to access MOUNTPOINT error

[thiagomajesk]

Hi! I'm having the following error trying to incorporate this image into my workflow:

Mounting bucket my-bucket-name onto /opt/s3fs/bucket, owner: 0:0
my-bucket-name-s3fs-1         | s3fs: unable to access MOUNTPOINT my-bucket-name: No such file or directory

The core idea is to have some data from Prometheus and Grafana stored into a S3 bucket.

This is a sample of my docker-compose.yml file:

services:
  s3fs:
    image: efrecon/s3fs:1.91
    restart: unless-stopped
    user: root
    cap_add:
      - SYS_ADMIN
    security_opt:
      - 'apparmor:unconfined'
    devices:
      - /dev/fuse
    environment:     
      S3FS_DEBUG: 1
      S3FS_ARGS: "-o nonempty"
      AWS_S3_BUCKET: $AWS_S3_BUCKET
      AWS_S3_ACCESS_KEY_ID: $AWS_S3_ACCESS_KEY_ID
      AWS_S3_SECRET_ACCESS_KEY: $AWS_S3_SECRET_ACCESS_KEY     
    volumes:
      - ./bucket:/opt/s3fs/bucket:rshared

  prometheus:
    image: prom/prometheus:latest
    user: root
    volumes:
      - ./bucket/prometheus:/etc/prometheus
      - ./bucket/prometheus-data:/prometheus
    command: --config.file=/etc/prometheus/prometheus.yml --web.config.file=/etc/prometheus/web.yml
    ports:
      - 9999:9090
    depends_on: ["s3fs"]

It seems it can't find the directory to mount, although from what I saw in the entry point file, the image tries to create the directory: https://github.com/efrecon/docker-s3fs-client/blob/master/docker-entrypoint.sh#L82-L85. I'm not a Docker expert, is there something else I should be doing to make this work properly?

[efrecon]

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

[cm91]

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...

[cm91]

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

[diepeterpan]

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

[efrecon]

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