Files
zeekayandHanzo Dev f4a6d50921 Report -visor so the guest names its own build
A sandbox that answers "-gvisor" is upstream's binary. Telling the two apart
by config is a guess — the RuntimeClass, the containerd entry and the shim
options can all name our binary while the pod runs something else, which is
exactly what happened when an inline BinaryName was accepted by containerd and
never read by the shim. The guest's own uname is the one answer that cannot be
wrong about which kernel is running it.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-09 01:48:04 -07:00
..