We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·Jun 17·5 min read
How Docker Desktop Networking Works Under the Hood (2022)
TL;DR
Docker Desktop faced a challenge where container traffic from a Linux virtual machine (VM) was not routed through corporate VPNs, limiting access to internal resources. To address this, Docker Desktop implemented vpnkit, a user-level TCP/IP stack that forwards traffic from the VM.
✦ Why It Matters
Engineers can now enable secure container networking without violating corporate VPN policies.
Key Takeaways
- Implement vpnkit for secure container networking
- Ensure compliance with corporate VPN policies
- Facilitate remote work for developers
- Enhance access to internal resources
Full Summary
Modern applications rely heavily on network connectivity, often requiring access to internal databases and external APIs. Docker Desktop, which uses a Linux VM to run containers, encountered issues with VPN policies that restricted traffic originating from the VM.
To solve this, Docker developed vpnkit, a TCP/IP stack written in OCaml, which operates at the user level and forwards traffic from the VM to the Internet. This approach ensures that all container traffic is routed correctly through the VPN, allowing seamless access to internal resources.
The implementation of vpnkit allows developers to work from various locations without compromising security. This solution not only enhances connectivity but also aligns with corporate security policies, ensuring that sensitive data remains protected.