33 ms·
The 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
by dozzie 9y ago
The 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 9y 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 9y agoIn other words, it's totally OK not to understand what you're working with?
- brudgers 9y agoBecause I can't write assembly for an i7 or demodulate 802.11N radio signals, intellectual honesty requires me to say yes.
- dozzie 9y 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.