Drew Erny
Software Engineer at Mirantis
Northport, Alabama, United States
Summary
🤩
Rockstar🎓
Top SchoolDrew Erny is a software engineer with 12 years of experience specializing in container orchestration, distributed systems, and backend/DevOps tooling. Currently remote at Docker (now Mirantis) he has worked deeply on the Moby, Swarmkit, and Docker CLI projects, contributing production-grade logging, service/task handling, and cluster management improvements to one of the most widely used container ecosystems. He is an active FLOSS contributor who helps others onboard to his projects and has a track record of hardening systems (TLS updates, graceful shutdowns, signal handling) and fixing subtle runtime issues like log hangs and election bugs. Based in Northport, Alabama and trained at the University of Alabama, he blends practical open-source stewardship with hands-on engineering across both user-facing CLIs and core orchestration primitives. Colleagues rely on him for pragmatic fixes and thoughtful refactors that improve reliability at scale.
12 years of coding experience
4 years of employment as a software developer
Bachelor of Science - BS, Computer Science, Bachelor of Science - BS, Computer Science at The University of Alabama
Github Skills (24)
container10
docker10
apidoc10
api-design10
distributed-systems10
dockers10
go10
api10
golang10
devops10
clustering10
swarm10
cli10
back-end-development9
tls129
Programming languages (9)
Github contributions (5)
moby/swarmkit
May 2016 - Jan 2023
A toolkit for orchestrating distributed systems at any scale. It includes primitives for node discovery, raft-based consensus, task scheduling and more.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:11 reviews, 353 commits, 435 PRs in 6 years 8 months
Contributions summary:Drew contributed to the Swarmkit project by addressing several bugs and implementing improvements to the project's functionality. Their contributions included cleanly shutting down the manager, gracefully handling SIGTERM signals, and preventing users from removing internal networks. They also added the functionality to implement a more robust task handling for replicated and global jobs.
schedulingconsensuspaxosscalediscovery
docker-archive/classicswarm
Jun 2016 - Sep 2019
Swarm Classic: a container clustering system. Not to be confused with Docker Swarm which is at https://github.com/docker/swarmkit
Role in this project:Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:11 commits, 12 PRs, 1 push in 3 years 2 months
Contributions summary:Drew primarily contributed to the backend of the Docker Swarm Classic project. Their work involved dropping support for older TLS versions and fixing an issue related to the primary cluster manager election. They also bumped the advertised API version and improved OS detection by incorporating supported platforms from the manifest. Additionally, the user updated vendoring dependencies for logrus and docker.
containersswarmdocker-swarmdockerclustering
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.