4 ms·
It's tempting to say that containers don't have any virtualization costs, but they often do for networking. For some applications, the addition of another netwo
by scott_s 8y ago
It's tempting to say that containers don't have any virtualization costs, but they often do for networking. For some applications, the addition of another networking driver doesn't matter. For others, it does.
- m0zg 8y agoThere is no "another networking driver" in containers. It's the same networking driver.
- scott_s 8y agoFor standard Docker container deployments, there is. See: https://docs.docker.com/network/ https://docs.docker.com/network/
- m0zg 8y agoThat's not a "driver" in the traditional sense, meaning it doesn't talk to the actual hardware directly. It's just a bridge or iptables.
- scott_s 8y agoshrug It's additional software in the networking stack, and it has a performance penalty. I think it's fair to call it a "virtualization cost," since you're paying for the container's networking abstraction.