-
Notifications
You must be signed in to change notification settings - Fork 67
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
Docker issues #165
Comments
@liske : Is there anything we could do to support progress? Is this something a PR would be accepted for? If so, should the solution be discussed in more detail prior to submitting a PR? |
First we need to get the root cause why needrestart does not detect the process as docker related and ignore those PIDs. The docker detection is based on cgroup name matching. Could you please provide the content of |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
Checking this on an CentOS 7.6 System:
Checking the cgroups of the Docker daemon:
Now checking the cgroups of a Docker container:
|
The cgroup naming style was not detected, yet. |
Hey,
we have some docker processes running which is fine so far, but, needrestart detects services running in a docker container and wants to restart docker itself.
docker itself should be restarted, if required but restarting it for it's processes/childs makes no sense. So they should be ignored or they should be restarted the proper way.
Here is an example
It may be related to #80
In this case it's a CentOS 7.6 system.
The text was updated successfully, but these errors were encountered: