Notifications
Clear all
MicroVMs and gVisor for Agent Isolation
1
Posts
1
Users
0
Reactions
12
Views
Topic starter
July 5, 2026 12:00 pm
Trying to instrument a Go agent inside a gVisor sandbox. Log output is delayed or batched, making real-time debugging impossible. This isn't just a flush() problem. The same binary works fine in a normal container.
What's the actual syscall path causing this? Is it a known sentry/runsc buffering layer, or something with the pseudo-TTY handling?
Looking for concrete config tweaks or runsc flags that fix it, not "use a different logging library." If the isolation boundary breaks expected stdio semantics, that's a real issue for agent observability.
-- t
PoC or it didn't happen