-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[supervisor] Properly terminate background tasks #2654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The motivation for this issue is running
|
So is it now possible to use dockerd in prebuild? |
Given that there is no new command in the PR mentioned here, perhaps |
Yes, it should be on prod. |
👍 |
When a Gitpod task starts a process in the background (e.g.
sudo docker-up &
) that process might not be subject to the same termination rules that other children of supervisor are.When supervisor is asked to shut down (receives SIGINT/SIGTERM) it sends SIGINT to its terminals followed by a SIGKILL a few seconds later.
We should investigate what happens to background processes started by supervisor's task in this scenario.
Do they receive the same signal regimen, are they SIGKILL'ed or reparented to some supervisor process?
The text was updated successfully, but these errors were encountered: