​

MinIO NAS Gateway

​

Run MinIO Gateway for NAS Storage

​

Using Docker

docker run -p 9000:9000 --name nas-s3 \
 -e "MINIO_ROOT_USER=minio" \
 -e "MINIO_ROOT_PASSWORD=minio123" \
 -v /shared/nasvol:/container/vol \
 minio/minio gateway nas /container/vol

​

Using Binary

export MINIO_ROOT_USER=minio
export MINIO_ROOT_PASSWORD=minio123
minio gateway nas /shared/nasvol

​

Test using MinIO Browser

​

Test using MinIO Client mc

​

Configure mc

mc alias set mynas http://gateway-ip:9000 access_key secret_key

​

List buckets on nas

mc ls mynas
[2017-02-22 01:50:43 PST]     0B ferenginar/
[2017-02-26 21:43:51 PST]     0B my-bucket/
[2017-02-26 22:10:11 PST]     0B test-bucket1/

​

Breaking changes

​

The file-based config settings are deprecated in NAS

​

Migration guide

notify_webhook:1 endpoint=http://localhost:8080/ auth_token= queue_limit=0 queue_dir=/tmp/webhk client_cert= client_key=

export MINIO_NOTIFY_WEBHOOK_ENABLE_1=on
export MINIO_NOTIFY_WEBHOOK_ENDPOINT_1=http://localhost:8080/
export MINIO_NOTIFY_WEBHOOK_QUEUE_DIR_1=/tmp/webhk

NOTE: Please check the docs for the corresponding ENV setting. Alternatively, We can obtain other ENVs in the form mc admin config set alias/ <sub-sys> --env

​

Symlink support

​

Behavior

• For reads symlink resolves to file symlink points to.
• For deletes
  • Delete of symlink deletes the symlink but not the real file to which the symlink points.
  • Delete of actual file automatically makes symlink’ed file invisible, dangling symlinks won’t be visible.

​

Caveats

• Disallows follow of directory symlinks to avoid security issues, and leaving them as is on namespace makes them very inconsistent.
• Dangling symlinks are ignored automatically.

​

Explore Further

• mc command-line interface
• aws command-line interface
• minio-go Go SDK