Advanced Docker developer workflows on Mac OS and Windows
Most developers use a Mac or Windows host to develop Docker Linux containers, which complicates filesystem sharing between the host and the Linux container and requires replicating Linux networking configuration locally. Anil Madhavapeddy and Richard Mortier outline ways to make using Docker on a Mac or Windows transparent, thus enabling a rapid test/edit/deployment cycle for microservices.
| Talk Title | Advanced Docker developer workflows on Mac OS and Windows |
| Speakers | Anil Madhavapeddy (Docker, Inc), Richard Mortier (University of Cambridge, UK) |
| Conference | O’Reilly Open Source Convention |
| Conf Tag | |
| Location | Austin, Texas |
| Date | May 16-19, 2016 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Most developers use a Mac or Windows host to develop Docker Linux containers. This normally requires the installation of a Linux virtual machine as well as a complicated setup that includes a local networked filesystem for sharing data between the host and the Linux container, including UID mapping and case sensitivity, with inotify often being unreliable into the container; replicating Linux networking configuration locally to reflect the structure of the deployed microservices on the local laptop; and maintaining a separate Linux virtual machine and hypervisor such as VirtualBox, leading to heavyweight resource usage on a developer laptop. Anil Madhavapeddy and Richard Mortier outline various methods to make using Docker on a Mac OS or Windows laptop as transparent as possible to the developer, including build scenarios from the conventional (Compose-based web stacks) to the deep end of systems (unikernel compilation) to the multi-CPU architecture (cross-compiling ARM containers on a normal Mac or Windows host).
