kata-containers/agent

agent should lock the subreaper thread

Closed this issue · 0 comments

Description of problem

Right now agent does not lock the OS thread in go runtime that is set to be a child subreaper. As a result, it is possible that the the underlying OS thread gets scheduled off and quits. Then we lose the subreaper OS thread and orphan threads will be reparented to init (e.g. systemd) and kata agent won't be able to catch the exit status.