2 ms·
Slide #40: Typical Workflow is, very much like some other aspects of docker (use of specific filesystems, use of entire filesystems within containers, etc.), a
by contingencies 13y ago
Slide #40: Typical Workflow is, very much like some other aspects of docker (use of specific filesystems, use of entire filesystems within containers, etc.), a false general case that is in fact unsuited to many people's requirements.
Slide #44: Docker roadmap towards 1.0 seems to dodge the question of significant differences in function with regards the apparent plan to adopt a variety of storage backends with different capabilities, use of different virtualization environments as targets, etc.
I support docker as a project but I still really think you guys need to stop and ponder your architecture and goals before charging along too far. For projects to survive long term and be useful sometimes separating concerns is necessary, and I would suggest that's perhaps not being done well at present with some one-size-fits-all assumptions that are pretty anti unix philosophy (do one thing and do it well). What is the one thing? Is that really a general need? In all cases? What does a user lose with this abstraction? Rather than increasing scope, what would happen if you tried lopping those bits off entirely?