Skip to content

fix(virtualized): detect gVisor more reliably, and introduce a maybe present state #34

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

Merged
merged 1 commit into from
Nov 10, 2024

Conversation

azenla
Copy link
Member

@azenla azenla commented Nov 10, 2024

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.

…present state

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.
@azenla azenla requested review from kaniini and jedsalazar November 10, 2024 10:25
Copy link
Contributor

@jedsalazar jedsalazar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@azenla azenla merged commit 391573d into main Nov 10, 2024
@azenla azenla deleted the virt-fixes branch November 10, 2024 13:40
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.

2 participants