9e64b9f3a5
When all container tasks finish, they release the mount which in turn will close the 9P session to the gofer. The gofer exits when the connection closes, triggering the gofer monitor. The gofer monitor will _think_ that the gofer died prematurely and destroy the container. Then when the caller attempts to wait for the container, e.g. to get the exit code, wait fails saying the container doesn't exist. Gofer monitor now just SIGKILLs the container, and let the normal teardown process to happen, which will evetually destroy the container at the right time. Also, fixed an issue with exec racing with container's init process exiting. Closes #1487 PiperOrigin-RevId: 335537350 |
||
|---|---|---|
| .. | ||
| boot | ||
| cgroup | ||
| cmd | ||
| config | ||
| console | ||
| container | ||
| flag | ||
| fsgofer | ||
| sandbox | ||
| specutils | ||
| BUILD | ||
| main.go | ||
| version.go | ||
| version_test.sh | ||