-
Notifications
You must be signed in to change notification settings - Fork 642
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
Config to specify isolation technology for container #1376
Conversation
876b781
to
99ad091
Compare
Codecov Report
@@ Coverage Diff @@
## master #1376 +/- ##
============================================
+ Coverage 59.03% 59.07% +0.04%
- Complexity 1985 1989 +4
============================================
Files 162 162
Lines 9023 9032 +9
Branches 1364 1365 +1
============================================
+ Hits 5327 5336 +9
Misses 3205 3205
Partials 491 491
|
Hi. Is there a way to reference the plugin built from this branch? |
I think https://jitpack.io/ might help |
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 a lot for the PR ! Sound reasonable to me, we will consider this for one of the next releases (but please note that this plugin is on low maintenance mode, which means things might take a bit longer than normally).
Do you know since which API version the Isolation
option is available for Docker ?
Kernel namespaces were introduced between kernel version 2.6.15 and 2.6.26. This means that since July 2008 (date of the 2.6.26 release ), namespace code has been exercised and scrutinized on a large number of production systems. Seems like docker allowed process isolation in this version Found this docker doc dated 2016 https://www.docker.com/sites/default/files/WP_IntrotoContainerSecurity_08.19.2016.pdf. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs |
@rhuss Any updates on possibility of getting this change in ? |
Sorry for late response. I think we should get this in for our upcoming release ( |
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.
Looks good to me, and I guess that since this feature is added on request, it's not harmful when running against an older Docker that is not supporting that parameter (as in this case the user needs to take care whether to configure Isolation
or not)
Please add a doc/changelog.md
entry, then I think we are good to merge.
Signed-off-by: Rahul Kulkarni <Rahul.Kulkarni@microfocus.com>
9b5fea4
to
1ad3cad
Compare
No description provided.