I'm sorry if I sounded condescending to you, but it's pretty clear that organizations with a strong engineering focus need a strong and clear vision of how comp

I'm sorry if I sounded condescending to you, but it's pretty clear that organizations with a strong engineering focus need a strong and clear vision of how components integrate - and the current state of docker actively discourages that. The ability to shove tools together willy-nilly, hacking around their incompatibilities, does not a solid platform create. Some of your biggest features, like the various networking modes, are complete misfeatures; The only reason you need bridge mode is bad network layout, the only reason for container is because you've screwed it up and you're using bridge mode. Both the dockerfile reference and run reference are incredibly long and filled with references to strange interactions with other features. The fact that features don't interact in ways that can be simply reasoned about but instead clarification is required is a huge red flag in core infrastructure. Docker has done wonderful things in terms of getting people to think about their services rather than their hosts. But each new feature reduces that advantage, as it allows people to take lazier approaches to integrate their systems, and those approaches flat-out don't work.