Andrew Kutz

Hi, I also would like to see `BeforeAll` implemented for the same reason. Sometimes standing up an environment is expensive.

Hi @DrewRay, Have you attempted using a config file at `/etc/rexray/config.yml`? ```yaml s3fs: accessKey: mask secretKey: mask options: -url=https://ooss.example.com/ ```

FWIW, I think a bug was introduced in 0.9 that is causing this to fail via the CLI. I am going to file this issue as a bug. I believe...

Thank you for finding this out!

It could be the permissions given to the container when it’s launched. The user that runs the container must be able to mount filesystems.

Hi @jzampieron, libStorage has been merged into REX-Ray as of 0.10.0. Please file any issues against REX-Ray. FWIW, libStorage's GH README does indicate this transition: 

Hi @sebglon, The plug-ins are not meant to access remote libStorage API endpoints, but rather are each a self-contained libStorage client and server. Thus no TLS is necessary. If you're...

Hi @sebglon, Also, if you want, you can always just place a file at `/etc/libstorage/tls/cacerts`. It will be detected and loaded as the `cacerts` file since that is the default...

Thank you @clintkitson. @sebglon, the libStorage client->server to which I referred is the same as Clint's statement: > TLS would be beneficial with plugins when they are communicating separately to...

Hi @sebglon, In your case the libStorage `cacerts` file will prove of little help. As I said, it's not for general TLS, only for libStorage's own client->server communiques. In your...