Hey,
I noticed how there were options to convertUnderscores for GCE and DO, it would be nice to have it for Amazon as well?
convertUnderscores option for Amazon? specifically for S3...
$ rexray version
REX-Ray
-------
Binary: /usr/bin/rexray
Flavor: client+agent+controller
SemVer: 0.11.0
OsArch: Linux-x86_64
Commit: 508023f4b0e4974f1844c26b39af7c4219f4c7a9
Formed: Mon, 16 Oct 2017 00:07:06 PDT
libstorage:
service: s3fs
s3fs:
accessKey: XXXX
secretKey: XXXX
endpoint: https://play.minio.io
region: us-east-1
disablePathStyle: false
options:
- url=https://play.minio.io
- use_path_request_style
- allow_other
- nonempty
Thanks for the feedback @khoanguyen96. Will discuss this for a future release.
I think I just hit just issue as a limitation which would make s3fs useless at this time for docker stacks.
When deploying stack swarm volume names are automatically prepended with the stack name. As seperator a '_' is used and that is not allowed as bucket name.
ID | f5jttun566wxhyx59ksy2ynjz
-- | --
State | rejected
State Message | preparing
Error message | create bushbaby-test-bushbaby-nl-service_webroot: VolumeDriver.Create: docker-legacy: Create: bushbaby-test-bushbaby-nl-service_webroot: failed: error creating s3 bucket
Image | nginx:latest
Slot | 1
Created | 2017-12-13 16:20:47
having the same issue on docker swarm stack volumes since they are prepended with stackname including a _ character getting the error
create Weblate_postgres-data: VolumeDriver.Create: docker-legacy: Create: Weblate_postgres-data: failed: error creating s3 bucket
Yep, I've just hit this as well. S3FS plugin is currently useless for swarm stacks because of the above reasons.
As a workaround, you can define a custom volume name as outlined here, but you will lose stack scoping (the volume name is used as is).
Has anyone made progress on this? I just ran into this issue. Doesn't seem like a very difficult PR, happy to do it if nobody has done so yet.
Most helpful comment
I think I just hit just issue as a limitation which would make s3fs useless at this time for docker stacks.
When deploying stack swarm volume names are automatically prepended with the stack name. As seperator a '_' is used and that is not allowed as bucket name.