forked from containers/common
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
aardvark,commit: acquire fs lock when performing commit
* We should avoid overriding configs when another instance of aardvark is trying to commit configs on the same path. * On certain system a race exists where more than one aardvark instance are started in the frame where one instance has not yet completed updating its `aardvark.pid` causing more than one instance to get started and eventually causing conflits on the requested ports. Some conditions are reported on `low power hardware which tries to start a significant amount of containers` and it looks like the case matches with what is described in the second point. Signed-off-by: Aditya R <arajan@redhat.com>
- Loading branch information
Showing
3 changed files
with
64 additions
and
0 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters