-
Notifications
You must be signed in to change notification settings - Fork 2k
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
exec driver leaks executor process after StartTask
error
#11958
Comments
Thanks for raising this @tantra35, from a quick look at the information you provided (thanks for all the details!) I suspect we're missing some clean-up in an error code path. |
@lgfa29 could you please tell is it possible expect a fix soon? |
We don't have a date for a fix. I placed this into our backlog for further triaging. |
Doing some issue cleanup and wanted to confirm that this is still the case even after some improvements we've made recently to the minimal jobspecjob "example" {
group "sleep" {
task "sleep" {
driver = "exec"
user = "ubuntu"
config {
command = "sleep"
args = ["300"]
cap_add = ["net_raw"]
}
}
}
} We get task events like the following (as expected):
But after a couple of restarts we get leaked
I'm going to re-title this slightly and mark it for roadmapping. I'll also note from a quick look at the code that it almost certainly impacts the |
StartTask
error
Nomad version
Output from
Nomad v1.1.10 (2f08fe230da05e1b179710ebe0e2582249599a4b+CHANGES)
Operating system and Environment details
Ubuntu 20.04
Issue
If we use unhallowed caps for exec driver after faill we got leeaking nomad exec processes
Reproduction steps
For example if we use
net_raw
caps that doens't allowed by default for exec driverafter allocation on node fail with follow task state(which is absolutely expected behavior)
on client node we got leaked
nomad executor
processes (here we demonstrate some output ofps axuf
)The text was updated successfully, but these errors were encountered: