stegololz opened a new pull request, #62992: URL: https://github.com/apache/airflow/pull/62992
Fix `breeze run` leaking a Docker network on every invocation Each `breeze run` creates a unique compose project (`breeze-run-<uuid>`) but never tears it down afterward. The `--rm` flag on `docker compose run` removes the container but not the network. Over time, stale networks accumulate and Docker's IPAM exhausts its default address pool. In my case, it ended with docker Docker allocate an ip identical to my wifi router's IP. This created a bridge interface that captured traffic meant for the real gateway, silently breaking all my IPv4 connectivity. My implementation wrap the command execution in `try/finally` and call `bring_compose_project_down` + `remove_docker_networks`, matching the existing pattern in [`testing_commands.py`](https://github.com/apache/airflow/blob/main/dev/breeze/src/airflow_breeze/commands/testing_commands.py). --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Claude Opus 4.6) Generated-by: Claude Code (Claude Opus 4.6) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
