Skip to content

fix: attach Airflow container to network before starting#143

Open
tpwo wants to merge 1 commit into
GoogleCloudPlatform:developmentfrom
tpwo:fix-container-race-condition
Open

fix: attach Airflow container to network before starting#143
tpwo wants to merge 1 commit into
GoogleCloudPlatform:developmentfrom
tpwo:fix-container-race-condition

Conversation

@tpwo

@tpwo tpwo commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Race condition on first start: entrypoint runs "airflow db migrate" immediately after container.start(), but network attachment happened after in Python code -- causing DNS resolution failure for the DB container hostname.

Attach the Airflow container to the Docker network while it is still in CREATED state, before calling container.start(), so the hostname is resolvable from the first instruction of the entrypoint.

Resolves #142.

New PR

Thank you for contributing!

  • (CONFIRMED) All contributions have to be merged to the development branch, please
    make sure you set it as the target of this PR.
  • Confirm you ran pytest tests and all the unit tests are green -- Tests are failing locally, but I found out that this is because of other reasons. I created a PR fix: correct integration test assertions for postgresql create #144 to fix tests.

Race condition on first start: entrypoint runs "airflow db migrate"
immediately after container.start(), but network attachment happened
after in Python code -- causing DNS resolution failure for the DB
container hostname.

Attach the Airflow container to the Docker network while it is still
in CREATED state, before calling container.start(), so the hostname is
resolvable from the first instruction of the entrypoint.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant