Writing

A Docker Networking Bug Made Me PyAirbyte's 7th External Contributor

Jun 21, 2024 · 2 min read

We were already using Airbyte, and PyAirbyte specifically for quick experiments: small enough to run outside the full platform, real enough to trust the output. The bug was ordinary: a source running in its own Docker container couldn't reach something on the host. The fix was a use_host_network argument on get_source(), and I sent it in as a pull request instead of just filing an issue.

Aaron Steers, PyAirbyte's maintainer, replied in Airbyte's Slack the same day it merged.

Aaron Steers announcing the merged PR, and telling Niyas he'd become PyAirbyte's 7th external contributor, in Airbyte's Slack

Four more pull requests followed over the next five months: the same host-network argument on get_destination(), an AIRBYTE_TEMP_DIR override, AIRBYTE_OFFLINE_MODE for air-gapped environments, and a psycopg version bump to keep it working on older macOS.

Airbyte's main project has 21,000+ stars. PyAirbyte is newer and smaller, its own library for running Airbyte's connectors directly in Python without the full platform. It didn't need a big audience to matter to me. I used it, hit rough edges, and fixed the ones I could.


Resources