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
Following the setcap
instruction raises 'fatal error: Invalid argument'
#2401
Comments
My first guess would be that Ubuntu 20.04 is just too old. Please retry with something newer. |
Thanks @adrianreber, it worked on 24.04. If |
Please close if resolved. |
My concern was that it was printing a wrong diagnostic message, sorry - I think it should emit a different message than 'setcap ...' if the capability was not available. The issue is not resolved yet. |
If your setcap is too old there is nothing CRIU can do. |
@aqjune if you don't like the error message, pls open a pull request with the fix. We will be glad to accept it. |
Description
When I try
criu dump
it requests that capability of CAP_SYS_ADMIN or CAP_CHECKPOINT_RESTORE must be given to criu, with an instruction showing how to usesetcap
. However, if I follow it, I am seeing the following error:This might not be a problem of criu (I found that criu's CI script is in fact using the same command), but was just wondering whether any further instruction could be given in the case, which might be helpful to beginners.
Describe the results you expected:
The
setcap
command is succesfully doneAdditional information you deem important (e.g. issue happens only occasionally):
CRIU logs and information:
criu 3.19
CRIU full dump/restore logs:
None
Output of `criu --version`:
Output of `criu check --all`:
Additional environment details:
The text was updated successfully, but these errors were encountered: