Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of docker: fix bug where network pause containers would be erroneously reconciled into release/1.4.x #16429

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #16352 to be assessed for backporting due to the inclusion of the label backport/1.4.x.

The below text is copied from the body of the original PR.


This PR adds tracking of pause containers to the docker driver, fixing a bug introduced by #15898 where the containers are now subject to dangling container reconciliation. The pause container created for allocs with docker tasks making use of bridge networking is not created in the same flow as a normal Task - which have a TaskHandle state. The set of tasks not to reconcile was identified by scanning the set of these states, which does not include pause containers.

To remedy this, this PR now tracks pause containers in their own little store. Since the Nomad Client may be restarted, we scan existing running containers on startup to reload the store from existing running containers.

Fixes: #16338

@hc-github-team-nomad-core hc-github-team-nomad-core force-pushed the backport/pause-reconciliation/preferably-intimate-humpback branch from a9186fd to 3293060 Compare March 10, 2023 21:22
@hc-github-team-nomad-core hc-github-team-nomad-core merged commit 6972a2e into release/1.4.x Mar 10, 2023
@hc-github-team-nomad-core hc-github-team-nomad-core deleted the backport/pause-reconciliation/preferably-intimate-humpback branch March 10, 2023 21:22
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.

None yet

2 participants