Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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


For standard Docker container deployments, there is. See: https://docs.docker.com/network/


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.


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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: