I found my codes by typing in docker logs minio. These are used by the client or the web front-end to connect securely. When you run Minio you will be issued a key and a secret. Let's imagine you have an SSD mounted at /mnt/sdd, then we can run the following to use it instead: # docker run -v /mnt/ssd:/export -p 9000:9000 -name minio -d minio/minio server /export The simplest set of overrides (above) would store all of your data inside the container, but we could probably use a bind-mount or Docker volume for that. # docker run -p 9000:9000 -name minio -d minio/minio server /export Since I'm a Docker Captain I'm going to opt for containers. Now you have a choice of running Minio in Docker or on your bare-metal.
If you're on a Mac then you can install it with brew: # brew install minio-mc This means that if you were thinking of building a Raspberry Pi NAS - it can be even easier to get started than with NFS or Samba. I found Minio easy to setup and liked the fact that it comes with sensible defaults. They've both easy to setup and if you're familiar with command-lines I think you will like working with it. Well Minio comes in two parts - the client portion and the server portion which also includes a web-ui / file-browser. Minio even has a very attractive UI and a test site available at If you deploy Minio onto one of your PCs or Raspberry Pis you can leverage that machine for storing data in your applications, photos, videos or even backing up your blog. I hope you find it useful and do follow me on Twitter and YouTube. This tutorial is a walk-through for deploying and using Minio.
Minio is a project that has come up on my radar several times and caught my attention - it's an S3-compatible object-storage server that you can run on your own kit and has first-class Docker and Raspberry Pi support.