search

machine-drivers / docker-machine-driver-xhyve

docker-machine/minikube/minishift driver plugin for xhyve/hyperkit (native macOS hypervisor.framework)
https://godoc.org/github.com/machine-drivers/docker-machine-driver-xhyve
BSD 3-Clause "New" or "Revised" License
888 stars 74 forks source link

Update readme to document rawdisk #173

Closed dalehamel closed 7 years ago

dalehamel commented 7 years ago

@zchee readme update as requested for https://github.com/zchee/docker-machine-driver-xhyve/pull/169

zchee commented 7 years ago

@dalehamel Thanks! merged.

alafon commented 7 years ago

@zchee I won't open a new issue to ask a possible simple question but could you explain a bit more what using this feature implies ? It is said that there is a potential cost of data durability, what does that mean ? Can mounted volumes be affected/corrupted ? Or is it just about the containers inner data ?

Thanks in advance

dalehamel commented 7 years ago

@alafon since I added the support for this, I'll answer.

Basically, if you are running something where data integrity really matters (MySQL perhaps), then an unclean shutdown of the VM could result in some bytes being unwritten when using this driver.

Most likely though, since you're probably using this for development, this probably doesn't matter.

This is because the virtio-blk is much more "raw" than the ahci approach, which attempts to more closely mimic how an actual SCSI device would operate.

We use virtio-blk because it is faster and lower overhead, and we make sure everything is disposable anyways (this is kubernetes after all), so we don't really care if there are some edge cases where data could be corrupted.

alafon commented 7 years ago

Thanks for the answer, pretty clear :)