4 ms·
To me, Docker has to balance creating a product that is accessible to individual developers by virtue of ease of use with exposing all the gory details of conta
by brudgers 10y ago
To me, Docker has to balance creating a product that is accessible to individual developers by virtue of ease of use with exposing all the gory details of containerization. Or to put it another way, Docker has to pick a level of abstraction over containers somewhere between a black box with a power button and cgroups. The behavior just falls closer to one end of the it-is-not-a-bug-it-is-a-feature spectrum than the other.
I mean Bell Labs old Unix hand levels of expertise are great, but the reality of "a good way to do it" should probably be tailored for users more toward the center of the bell curve.
- dozzie 10y agoThe problem is that Docker hides from its users details about network configuration, the same details that the users should understand and should know about. It's just bound to fail in any scenario other than Docker authors envisoned. All in the name of assumption that the users -- programmers working with network! -- are too dumb to configure network.
- brudgers 10y agoIf Docker required users to be fluent in the differences between UFW and IPtables, the user base would be much smaller than it is currently.
- dozzie 10y agoIn other words, it's totally OK not to understand what you're working with?
- brudgers 10y agoBecause I can't write assembly for an i7 or demodulate 802.11N radio signals, intellectual honesty requires me to say yes.
- dozzie 10y agoDo you apply the same approach to other tools? You don't know how to call a compiler? Don't know how to write a set of rules for your build system? Don't know how external libraries are loaded? Because if you work with network, not understanding how to set up a NAT and port forwarding is in the same category as not knowing how module search path works in your chosen runtime. It's not several levels lower, contrary to your missed analogy.