-
Notifications
You must be signed in to change notification settings - Fork 27
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
✨Propagate capabilities to correct processes #4225
✨Propagate capabilities to correct processes #4225
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4225 +/- ##
=========================================
+ Coverage 84.9% 86.0% +1.1%
=========================================
Files 940 152 -788
Lines 41064 8265 -32799
Branches 953 0 -953
=========================================
- Hits 34882 7112 -27770
+ Misses 5978 1153 -4825
+ Partials 204 0 -204
Flags with carried forward coverage won't be shown. Click here to find out more.
|
…rc-simcore-forked into pr-osparc-docker-exec-cap-add
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.
if possible remove the hard-coded 3.10
Code Climate has analyzed commit f05f124 and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What do these changes do?
In theory capabilities appear to be very simple at a first glance. They do hide some awkward interactions.
Why were capabilities not being propagated before?
gosu
which drops thempython
executableWe can see the
CapPrm
fields containing only the given capability for the python interpreter started processes and subprocesses.Reference material:
Related issue/s
How to test
DevOps Checklist