You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 12, 2020. It is now read-only.
Recently, during the process of using drone (version 0.8.10), I found that there are a large number of unix domain sockets in the drone-agent process, and the number is more than 18000+. This is obviously not a normal phenomenon, which means , The docker client (that is, drone-agent) did not release the socket link between it and the dockerd process, and further, there was a leakage problem.
At first, I tried to upgrade the docker version to docker-ce 19.03.8, but the problem remained. Later, by tracing Drone's code, I found that it used the source package cncd/pipeline. However, the functions provided by this package do not provide the Close socket capability. I did a fix in my production environment and the problem was solved.
Originally I wanted to submit a PR, but I saw that there was already a PR trying to fix this problem #20 . The socket leakage problem is a bit serious, so I have 2 problems:
Why is this PR not merged?
Does the owner of this project still plan to fix this problem, and does it require me to submit a PR again?
The text was updated successfully, but these errors were encountered:
Recently, during the process of using drone (version 0.8.10), I found that there are a large number of unix domain sockets in the drone-agent process, and the number is more than 18000+. This is obviously not a normal phenomenon, which means , The docker client (that is, drone-agent) did not release the socket link between it and the dockerd process, and further, there was a leakage problem.
At first, I tried to upgrade the docker version to docker-ce 19.03.8, but the problem remained. Later, by tracing Drone's code, I found that it used the source package cncd/pipeline. However, the functions provided by this package do not provide the Close socket capability. I did a fix in my production environment and the problem was solved.
Originally I wanted to submit a PR, but I saw that there was already a PR trying to fix this problem #20 . The socket leakage problem is a bit serious, so I have 2 problems:
The text was updated successfully, but these errors were encountered: