UPDATE (February 2021): We migrated the demo to our new 3.0 release.
Being developers and sysadmins ourselves, we like software that we can just test quickly in a container. That’s why we decided to bring you a single container demo of Quobyte.
This demo will start a container with all Quobyte services and the Quobyte client. With the bidirectional volume mapping you can even access the Quobyte mount directly from your host OS. The setup looks like this:
Please keep in mind that this is a purely functional demo. Since the data is stored inside the container image the performance will be very limited. Also, this demo has just one container so you won’t get the benefits of Quobyte’s linear scalability for performance and also no fault tolerance! Unless you take a snapshot of the container before shutdown, your data will also be lost.
You need a Linux distro with docker version 19.03 or newer like CentOS 7 and your user must be able to talk to the docker daemon. With that said, time to get started. Run the following commands to start the demo:
mkdir -p $HOME/quobyte-mnt && \ docker run -d --rm --name qs -p 8080:8080 \ --mount type=bind,source=$HOME/quobyte-mnt,target=/quobyte,bind-propagation=rshared \ --device /dev/fuse --cap-add SYS_ADMIN -e QUOBYTE_REGISTRY=127.0.0.1 \ --security-opt apparmor:unconfined -e QUOBYTE_HOST_UIDS="$USER:$UID:$USER:7777" \ quay.io/quobyte/quobyte-instant-demo:3.0.pre \ && docker logs -f qs
The first command creates the mount directory in your home. The second command starts the Quobyte demo docker container, forwards port 8080 for the web interface and binds the mount directory in a bi-directional mapping inside the container. Finally, the QUOBYTE_HOST_UIDS is a way to pass your username into the container to make sure a user with the same name exists there as well. The last command finally shows the output from the container.
Once the demo is ready you can cd ~/quobyte-mnt and use the Quobyte mount like any other file system. If you want, you can access the same mount from inside the container with docker -ti qs /bin/bash”.
The webconsole is running on http://localhost:8080 and the command line tool “qmgmt” can be used from inside the container.
If you want to see all of Quobyte on your bare metal, take our installer to get up and running in a few minutes:
For the cloud native enthusiasts, we also have container images on quay.io, our kubernetes operator to run Quobyte clients and servers fully automated inside k8s and finally our CSI plugin to map persistent volume claims to Quobyte with auto provisioning:
We always like to hear from you, so if you have feedback for us write to email@example.com!