-
Notifications
You must be signed in to change notification settings - Fork 346
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
Fix TestContainerNoBinaryExists test, by making create behaviour similar to runc #1347
Conversation
…has incorrect permissions Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1347 +/- ##
==========================================
- Coverage 68.73% 68.48% -0.26%
==========================================
Files 119 119
Lines 12601 12646 +45
==========================================
- Hits 8661 8660 -1
- Misses 3940 3986 +46 |
@utam0k I validated it with runc, and that too fails the test. The problem behind it is that we are validating the binary to be run in the init process exists, but the tests does not setup the binary at all. If we want to follow runc, we can skip this test, or we can choose to ignore the test in containerd validation. Unfortunately we have to make a call here. 😢 😭 |
@YJDoc2 Thanks for the great investigation. I vote for skipping it |
@kzys May I ask you to help us? Is |
Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com>
Let me take a look this week. We are at least using |
🙏 Thanks. |
@utam0k after checking runc repo, I don't think they are using oci-integration tests anywhere in their CI or makefile. they seem to be using their self-written tests for integration. |
@kzys Sorry, I thought we were talking about containerd, but we were talking about something else. I was mistaken🙇 Never mind. |
7f17c27
to
08dda37
Compare
Signed-off-by: Yashodhan Joshi <yjdoc2@gmail.com>
08dda37
to
ccf92b3
Compare
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.
Thanks!
When creating, this will check if the binary to run as container process exists and if it has proper permissions in the init process.
If it doesn't, then generate an error in create.
Signed-off-by: Yashodhan Joshi yjdoc2@gmail.com