-
Notifications
You must be signed in to change notification settings - Fork 1.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
git-remote-http zombies #441
Comments
+1 on this Issue I have seen this issue caused by a network interruption and as well firewall misconfiguration. It seems that an http timeout retrieving vulnerability data results in these processes, and they do not clear until the Clair container is restarted. |
Thanks for the report. I have some other projects that shell out to git that have had similar issues in the past. I'll see if I can share that code with this project to make our handling of git more robust. |
@jzelinskie I have found that making the entrypoint of the container Yelp's dumb-init mitigates the issue. I am running Clair as part of Vmware Harbor and submitted this PR goharbor/harbor#3361 . Hope that helps |
Also opened #477 |
It appears to me that git is the one creating the zombies, so then the (merged) dumb-init is the fix, right? |
This is correct. We now have an init system to reap these zombies. |
We just run into this with Clair quay.io/coreos/clair:v2.0.4. While this was merged almost a year ago the recently published image still don't contain this fix. See the manifest for v2.0.7 from 7 days ago: https://quay.io/repository/coreos/clair/manifest/sha256:931edc5abc036bcc6cd8316e54217958fe27c00f71bbf45c72814563c6acd088 |
Would you mind reopening this bug until the published images actually reflect that change? |
A
ps
listing on my machine showed a lot of zombie processes, all children of the main clair processeg
They're all dated "Aug01", starting from 8:15 through to 13:15 UTC, pretty much 2 every 10 minutes.
There might have been some networking issues around that time; I wasn't paying attention (this server is behind at least 2 layers of proxy).
If it helps identify the version
The text was updated successfully, but these errors were encountered: