3 ms·

There is no "another networking driver" in containers. It's the same networking driver.

• scott_s 8y ago
  For standard Docker container deployments, there is. See: https://docs.docker.com/network/ https://docs.docker.com/network/
  • m0zg 8y ago
    That'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 ago
      shrug 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.