https://github.com/ailispaw/rexray-barge
REX-Ray on Barge with Vagrant
https://github.com/ailispaw/rexray-barge
barge docker rex-ray vagrant
Last synced: 3 months ago
JSON representation
REX-Ray on Barge with Vagrant
- Host: GitHub
- URL: https://github.com/ailispaw/rexray-barge
- Owner: ailispaw
- Created: 2016-06-09T16:48:35.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2019-01-15T18:55:22.000Z (over 7 years ago)
- Last Synced: 2025-06-30T16:50:47.732Z (about 1 year ago)
- Topics: barge, docker, rex-ray, vagrant
- Size: 18.6 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# REX-Ray on Barge with Vagrant
[REX-Ray](https://github.com/emccode/rexray) allows us to create and attach a VMDK (Virtual Machine Disk) dynamically with [VirtualBox](https://www.virtualbox.org/) as a persistent volume for a container.
This shows how to use REX-Ray on [Barge](https://atlas.hashicorp.com/ailispaw/boxes/barge) with [Vagrant](https://www.vagrantup.com/) instantly.
It's inspired by
- [Discovering Docker Volume Plugins and Applications with VirtualBox | EMC {code} – Blog](https://blog.emccode.com/2016/01/06/discovering-docker-volume-plugins-and-applications-with-virtualbox/)
- [Volume Plugins with Docker Toolbox and Boot2Docker | EMC {code} – Blog](https://blog.emccode.com/2016/01/19/volume-plugins-with-docker-toolbox-and-boot2docker/)
Please read them for further details.
## Requirements
- [VirtualBox](https://www.virtualbox.org/)
- [Vagrant](https://www.vagrantup.com/)
- [vagrant-triggers](https://github.com/emyl/vagrant-triggers)
It's used to start/stop vboxwebsrv automatically.
I have tested it on Mac OSX, so you may need to modify Vagrantfile for the other platforms.
## Boot up
```bash
$ vagrant up
```
That's it.
## A sample use case
### Create a volume with REX-Ray
```bash
$ docker volume create --driver=rexray --name=mysql --opt=size=10
mysql
$ docker volume ls
DRIVER VOLUME NAME
rexray barge-packer-disk1.vmdk
rexray mysql
$ ls -l "$HOME/VirtualBox Volumes"
total 2688
-rw------- 1 ailispaw staff 1.3M Jun 9 09:55 mysql
```
`$HOME/VirtualBox Volumes` is defined in [assets/config.yml](assets/config.yml). You can change the location anywhere you want.
### Run a MariaDB container with the volume
```bash
$ docker run -d --volume-driver=rexray -e MYSQL_ROOT_PASSWORD=test -v mysql:/var/lib/mysql -p 3306:3306 --name mariadb mariadb
$ docker exec mariadb ls -l /var/lib/mysql
total 110644
-rw-rw---- 1 mysql mysql 16384 Jun 9 15:02 aria_log.00000001
-rw-rw---- 1 mysql mysql 52 Jun 9 15:02 aria_log_control
-rw-rw---- 1 mysql mysql 50331648 Jun 9 16:04 ib_logfile0
-rw-rw---- 1 mysql mysql 50331648 Jun 9 15:00 ib_logfile1
-rw-rw---- 1 mysql mysql 12582912 Jun 9 16:04 ibdata1
-rw-rw---- 1 mysql mysql 0 Jun 9 15:00 multi-master.info
drwx------ 2 mysql mysql 4096 Jun 9 15:00 mysql
drwx------ 2 mysql mysql 4096 Jun 9 15:00 performance_schema
-rw-rw---- 1 mysql mysql 24576 Jun 9 16:04 tc.log
```
### Check the contents of the volume
```bash
$ docker run --rm --volume-driver=rexray -v mysql:/mysql busybox ls -l /mysql
total 110644
-rw-rw---- 1 999 999 16384 Jun 9 15:02 aria_log.00000001
-rw-rw---- 1 999 999 52 Jun 9 15:02 aria_log_control
-rw-rw---- 1 999 999 50331648 Jun 9 16:04 ib_logfile0
-rw-rw---- 1 999 999 50331648 Jun 9 15:00 ib_logfile1
-rw-rw---- 1 999 999 12582912 Jun 9 16:04 ibdata1
-rw-rw---- 1 999 999 0 Jun 9 15:00 multi-master.info
drwx------ 2 999 999 4096 Jun 9 15:00 mysql
drwx------ 2 999 999 4096 Jun 9 15:00 performance_schema
-rw-rw---- 1 999 999 24576 Jun 9 16:04 tc.log
```
## Notes
- To dettach the VMDK(volume) from the VM, stop all containers with the volume. It will just dettach the VMDK, not remove from your local disk. See also [Ignore Used Count](http://rexray.readthedocs.io/en/stable/user-guide/config/#ignore-used-count) option.
- `docker volume rm ` will remove the volume from the list of Docker volumes and the VMDK from your local disk as well. You can set [Disable Remove](http://rexray.readthedocs.io/en/stable/user-guide/config/#disable-remove) option to disable it.
- The VMDK(volume) will be removed on `vagrant destoroy` unless you stop containers with the volume in advance of it, because `vagrant destoroy` will remove all attached virtual disks in the VM.
- The VMDK(volume) can be re-used only while VBoxSVC daemon is up. You can see the VMDK in the VirtualBox Media Manager and the volume in the list of Docker volumes. Otherwise VirtualBox will release the VMDK ~~and it won't be re-attached, and you can't use the volume again. H'm~~.