Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Fix the issue that ctrl-c stop vmcache server will stop all containers that its VM is created by it #1727

Merged
merged 2 commits into from
May 24, 2019

Conversation

teawater
Copy link
Member

No description provided.

There is an issue that ctrl-c stop vmcache server will stop all
containers that its VM is created by it.
The cause is kata-proxy and vmcache server use same tty, for example:
ps -e | grep kata
3617 pts/5    00:00:00 kata-runtime
3636 pts/5    00:00:00 kata-proxy
Ctrl-c will send signal to both kata-proxy and vmcache server.
Then the containers that its VM is created by this vmcache server will
quit with it.

Set Setsid to true when exec kata-proxy to handle this issue.

Fixes: kata-containers#1726

Signed-off-by: Hui Zhu <[email protected]>
After previous commit, found that kata-proxy is not quit
when vmcache server is stopped by ctrl-c.
The cause is current kata-proxy is setsid when it exec.  It will
not get the signal ctrl-c.

Call vm.Disconnect() when close vm in cache factory to handle
this issue.

Fixes: kata-containers#1726

Signed-off-by: Hui Zhu <[email protected]>
@teawater
Copy link
Member Author

/test

@teawater
Copy link
Member Author

/test

@devimc devimc merged commit 7fdda28 into kata-containers:master May 24, 2019
This was referenced Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants