-
Notifications
You must be signed in to change notification settings - Fork 902
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
Add runc to the list of possible container entrypoint parents #712
Conversation
LGTM label has been added. Git tree hash: 7b5aa33ff18ffbf98376d5bd754a2d68b9040acf
|
Great @mattpag ! Good catch! |
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!
@mattpag thanks! Could you please rebase it? |
Docker versions >= 18.09 removed the "docker-" prefix, so include runc in the list. Signed-off-by: Mattia Pagnozzi <mattia.pagnozzi@gmail.com>
f826775
to
221d641
Compare
@leodido done |
LGTM label has been added. Git tree hash: f05562ff2c4a14b7328157fca413d5a947e7d6de
|
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fntlnz, Kaizhe, leodido The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind rule-update
Any specific area of the project related to this PR?
/area rules
What this PR does / why we need it:
Add
runc
to the list of possible parents in thecontainer_entrypoint
macro since thedocker-
prefix added to the binary has been removed starting with Docker CE version 18.09.Without this, rules like "Terminal shell in container" were not triggered when expected while using recent Docker releases.
See https://github.com/docker/docker-ce/releases/tag/v18.09.0 ("Remove 'docker-' prefix for containerd and runc binaries docker-archive/engine#61 / moby/moby#37907, docker/docker-ce-packaging#241")
Special notes for your reviewer:
Does this PR introduce a user-facing change?: