Abstract

This article highlights issues that arise when deploying network address translation middle-boxes through containers. We focus on Docker as the container technology of choice and present a thorough analysis of its networking model, with special attention to the default bridge network driver that is used to implement network address translation functionality. We discuss some unexpected shortcomings we identified and elaborate on the suitability of containers for deploying services based on the Interactive Connectivity Establishment standard protocol. To support our findings, we present experiments we conducted in a real-world operational environment, namely a WebRTC service based on the Janus media server.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.