rexray: rexray/s3fs:0.11.2 could not create /data directory in s3.
Summary
rexray/s3fs:0.11.2 could not create /data directory in s3.
Bug Reports
I am using rexray/s3fs with docker plugin. When I tried 0.11.1, it was working well. When I using latest version of rexray/s3fs it was not working. so I checked the version and it was 0.11.2 updated 3days ago. In this version, it creates s3 bucket but could not create /data in bucket. and could not remount it.
Version
docker plugin: rexray/s3fs:0.11.2
Call sequence
$ docker plugin install rexray/s3fs \
> --grant-all-permissions \
> S3FS_REGION=ap-southeast-1 \
> S3FS_ENDPOINT=s3.ap-southeast-1.amazonaws.com \
> S3FS_ACCESSKEY=access \
> S3FS_SECRETKEY=secret+
latest: Pulling from rexray/s3fs
abc12345d458: Download complete
Digest: sha256:b3a2d374d8dedf8648679d5c8c69f5cb2c57e2c27a60678a1c5164f4d137cd17
Status: Downloaded newer image for rexray/s3fs:latest
Installed plugin rexray/s3fs
$ docker volume create -d rexray/s3fs --name rex-t4
rex-t4
$ docker run -it --rm -v rex-t4 alpine
# echo hello > /rex-t4/world.txt
# exit
$ docker run -it --rm -v rex-t4:/rex alpine
/run/torcx/bin/docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/9d4afe70f797cb98f9576c8ede30ce794a2b436c7237c29865bec261a2f8f566/rootfs': VolumeDriver.Mount: docker-legacy: Mount: rex-t4: failed: error mounting s3fs bucket.
ERRO[0001] error waiting for container: context canceled
Configuration Files
in docker plugin directory
rexray:
loglevel: warn
libstorage:
service: s3fs
integration:
volume:
operations:
create:
default:
fsType: ext4
mount:
preempt: false
server:
services:
s3fs:
driver: s3fs
Logs
/run/torcx/bin/docker: Error response from daemon: error while mounting volume '/var/lib/docker/plugins/9d4afe70f797cb98f9576c8ede30ce794a2b436c7237c29865bec261a2f8f566/rootfs': VolumeDriver.Mount: docker-legacy: Mount: rex-t4: failed: error mounting s3fs bucket.
ERRO[0001] error waiting for container: context canceled.
Plugin inspect
Service Log
About this issue
- Original URL
- State: open
- Created 6 years ago
- Comments: 18 (6 by maintainers)
Hello,
Having the same issue here.
With the rexray/s3fs:0.11.4 (latest as of February 2019) stand-alone Docker Plugin, the s3 bucket is not mounted. Instead the mountpoint is “local”, despite that inspecting the volume the correct s3fs driver is listed.
Not a credentials problem.
Mounting the bucket with the same config and Mount flags work in the host.
I believe there is some hidden state with respect to volumes, where multiple instances of the plugin start to cause the error mounting buckets.
Multiple versions or instances of the plugin can be created either via
docker plugin install --aliasordocker plugin rm/install.Messages such as
Error response from daemon: plugin rexray/s3fs:latest is in usewhen attempting to disable plugins make me suspect that there is volume state not represented indocker volume ls.It seems to be especially problematic when the different versions are using the same S3 account, because they are wanting to have multiple volumes with the same name.
Avoiding
--aliasseems to help. And restarting the docker engine afterdocker plugin rmseems to reset this hidden state.Yes, latest version didn’t work to create new volume and mount that volume. I am still using
rexray/s3fs:0.11.1.I attached a scenario for the latest version of
rexray /s3fs.