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

[TRACKING] Improve container engine state handling #1708

Open
incertum opened this issue Feb 26, 2024 · 3 comments
Open

[TRACKING] Improve container engine state handling #1708

incertum opened this issue Feb 26, 2024 · 3 comments
Labels
kind/feature New feature or request

Comments

@incertum
Copy link
Contributor

Motivation

We have identified a few areas of improvements wrt to state handling during the container lookup cycle, see #1595 (comment).

This issue serves to track progress in this regard.

It is also related to #291.

@gnosek @therealbobo @mstemm @leogr

@incertum
Copy link
Contributor Author

Please also explore #1707: It's incorrect to initialize a lookup to SUCCESSFUL, by the way. I believe this is the strongest indication of a very suboptimal shared design across the container engines we support.

@poiana
Copy link
Contributor

poiana commented May 26, 2024

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@incertum
Copy link
Contributor Author

/remove-lifecycle stale

Will get back to it soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants