3 ms·
Easy on the surface, but very limiting and frustrating in practice. I think all the energy spent around designing image layer file system after image layer fil
by davexunit 10y ago
Easy on the surface, but very limiting and frustrating in practice.
I think all the energy spent around designing image layer file system after image layer file system is good evidence that the Docker approach isn't as easy as it may seem.
- gourao 10y agoInteresting thought, however I think that the existing graph driver file systems are not actually an "image layer file system"... instead they are a general purpose file systems that are being used to store images. For example, what one wants with launching multiple instances of an image is to be able to clone the image. Today, to accomplish that, file system snapshots are used to simulate this feature. And that is where a lot of the problems start happening. LCFS does things purpose built for these use cases.
- jjobi 10y agoI would say image layer file system is not that hard to solve if you approach the problem correctly. It looks like all prior attempts tried to use general purpose solutions and in some cases a combination of those (for example, overlay on top of ext4) for dealing with a much smaller problem and ran into unnecessary complications. A lot of the complexities in a general purpose solution is unwarranted for a image layering file system. We looked at the requirements of a docker storage driver and built a solution from scratch, just to address those efficiently and nothing else.