3 ms·
Quick answer - given by a docker developer here. Use native devicemapper (using an lvm mounted volume). Best, fastest and least buggy. Overlay was flagged as
by sandGorgon 11y ago
Quick answer - given by a docker developer here.
Use native devicemapper (using an lvm mounted volume). Best, fastest and least buggy.
Overlay was flagged as massively buggy.
- contingencies 11y agoOverlay was flagged as massively buggy. Source? I was not planning to use LVM because it's documented[0] as slow and resource hungry... full copy each time, massive memory use, etc. CONFIG_OVERLAY_FS is mainline kernel code (unlike aufs) and not marked as experimental so if docker's implementation is buggy it is more likely to be docker's fault. It is documented by docker as being generally fast.[1] Regardless, I don't see performance as a great concern for my workloads... I'm more interested in the workflow enhancements. [0] https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/#other-device-mapper-performance-considerations https://docs.docker.com/engine/userguide/storagedriver/devic... [1] https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/#overlayfs-and-docker-performance https://docs.docker.com/engine/userguide/storagedriver/overl...
- sandGorgon 11y agohttps://news.ycombinator.com/item?id=11040097 https://news.ycombinator.com/item?id=11040097 I shifted from overlay to devicemapper after this conversation. YMMV.