-
Notifications
You must be signed in to change notification settings - Fork 2.2k
runc: remove --criu option #3353
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
Conversation
This was introduced in an initial commit, back in the day when criu was a highly experimental thing. Today it's not; most users who need it have it packaged by their distro vendor. The usual way to run a binary is to look it up in directories listed in $PATH. This is flexible enough and allows for multiple scenarios (custom binaries, extra binaries, etc.). This is the way criu should be run. Make --criu a hidden option (thus removing it from help). Remove the option from man pages, integration tests, etc. Remove all traces of CriuPath from data structures. Add a warning that --criu is ignored and will be removed. Signed-off-by: Kir Kolyshkin <[email protected]>
|
This should be done 5 years ago but I guess better late than never. runc also uses |
|
|
||
| ## [Unreleased] | ||
|
|
||
| ### Deprecated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can be another PR, but maybe we should have docs/deprecation.md in addition to docs/experimental.md ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know. It seems easy enough to search CHANGELOG.md for eprecat.
|
Now, an alternative would be to honor
-runc --criu /some/custom/criu/dir/criu ...
+PATH=/some/custom/criu/dir:$PATH runc(or a two-liner if The only question is, should using |
|
LGTM |
|
I guess this is fine, as the flag is still present (so things won't hard-fail). I stumbled upon this option in containerd, which (I think) may be using this flag; https://github.com/containerd/containerd/blob/77d53d2d230c3bcd3f02e6f493019a72905c875b/cmd/containerd-shim/main_unix.go#L60 Originally added in containerd/containerd@ab0cb4e, and I can see the So that code probably should be removed, and the option deprecated on containerd's side as well, @AkihiroSuda |
|
Opened containerd/go-runc#82 and containerd/containerd#6496 |
thaJeztah
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@AkihiroSuda @cyphar good to go? |
|
@adrianreber PTAL |
This was introduced in an initial commit, back in the day when criu was
a highly experimental thing. Today it's not; most users who need it have
it packaged by their distro vendor.
The usual way to run a binary is to look it up in directories listed in
$PATH. This is flexible enough and allows for multiple scenarios (custom
binaries, extra binaries, etc.). This is the way criu should be run.
Make
--criua hidden option (thus removing it from help). Remove theoption from man pages, integration tests, etc. Remove all traces of
CriuPath from data structures.
Add a warning that
--criuis ignored and will be removed.This used to be part of #3316.