fix(virtualized): detect gVisor more reliably, and introduce a maybe present state #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Inherently, detecting running under virtualization is hard on some virtualization runtimes. This change attempts to improve that situation by detecting container runtime env vars, and detecting gVisor using /proc/cmdline. Kata Containers cannot be reliably determined using this version of Am I Isolated, but the fallback uptime check test might present a maybe present result, to indicate that signs were detected.