-
Notifications
You must be signed in to change notification settings - Fork 73
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
Support restarting LXD-based containers #26
Comments
LXD does not implement containers itself but uses LXC in the background. So there is no need to support LXD explicitly, isn't it? Do you have a LXD environment available and did you give the most recent needrestart a try? |
Sort of. LXD uses liblxc but none of the old LXC command-line tools. So for example, Even if it was installed, I am not sure if this is advisable or supportable or if it even works. I think the LXD daemon assumes it has full control over the state of the containers under its control. See for example the container state management here https://github.com/lxc/lxd/blob/8d58e07c63808b0f13bdf8777fcfe7edcdb352f0/lxd/container_state.go which uses LXD-specific configuration variables, LXD-specific logging, and so forth. That said, I couldn't find any documentation/guidance on whether this is actually not supported or not. (They do recommend not mixing LXC and LXD in other ways, e.g. lxc/incus@33bc6b9 ). |
Did you try to run Could you please provide the content |
Here are the contents of a process within a LXD container that needrestart wants to restart. container is the name of the container the process runs in.
|
As per:
https://github.com/liske/needrestart/blob/f9cd0d3169be4eda7cf84357072ff935c81e9b5d/README.Cont.md
it is stated that there is container support for restarting containers. Notably absent is LXD: https://linuxcontainers.org/lxd/
If an LXD container is in use, the command for restarting it would be:
The text was updated successfully, but these errors were encountered: