-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Revert to using isolated PID namespaces in Docker #51634
Revert to using isolated PID namespaces in Docker #51634
Conversation
looks like maybe the e2e node test doesn't set the flag. Will look into it tomorrow. |
poke when tests pass, thanks for making the update. |
@verb do we want to specify the docker versions needed for the shared pid flag to work in the release note? |
@dims oh yes, great catch. Updated the release note. |
@yguo0905 can you offer any advice about how to best to update the node e2e test for this? It looks like the kubelet is only run one time for the test, so I can't test with both the flag enabled and disabled. Should I test the default behavior or test the feature even though it's disabled by default? I assume the former but I want to make sure I'm not missing something. |
I think we want to test this behavior because user can enable it if they want. We can set the flag at
|
/retest |
1 similar comment
/retest |
@@ -155,6 +155,7 @@ func (e *E2EServices) startKubelet() (*server, error) { | |||
"--serialize-image-pulls", "false", | |||
"--pod-manifest-path", manifestPath, | |||
"--file-check-frequency", "10s", // Check file frequently so tests won't wait too long | |||
"--docker-disable-shared-pid=false", |
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 we set it here we don't need the change in test/e2e_node/jenkins/jenkins-pull.properties
?
Actually, if we don't set it here there are other properties
files in test/e2e_node/jenkins/
need to be changed.
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.
Ok, thanks. Based on this advice (and because it made the e2e node test pass) I've removed the jenkins config and set the flag here.
A shared PID namespace were enabled by default in the 1.7 when running with a supported Docker runtime, but a Docker version that supports a shared namespace was not qualified for use. Release 1.8 will qualify a docker version supporting shared PID, but we don't want to cause disruption for container images which expect always to have PID 1.
This also renames isSharedPIDNamespaceEnabled() to isSharedPIDNamespaceSupported() to be more accurate.
48f203e
to
765374c
Compare
/retest
… |
/retest |
1 similar comment
/retest |
This PR is ready for review. According to sig-testing, pull-kubernetes-e2e-kops-aws is broken and has been disabled for the merge queue. This PR should be added to the 1.8 milestone to resolve critical-urgent issue #48937. |
@kubernetes/sig-release-members Can you please apply milestone v1.8? |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: derekwaynecarr, verb Associated issue: 48937 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
/retest |
/retest Review the full test history for this PR. |
@verb: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Automatic merge from submit-queue (batch tested with PRs 51984, 51351, 51873, 51795, 51634) |
@verb could you please assign a SIG to this? |
/sig node |
In 1.7 release the shared namespace is enabled by default. This is causing a problem when running pbench container which runs systemd. Related issue in upstream kubernetes: kubernetes/kubernetes#48937 According to my understanding this will be fixed from 1.8 with the following patch: kubernetes/kubernetes#51634
In 1.7 release the shared PID namespaces is enabled by default. This is causing a problem when running pbench container which runs systemd. Related issue in upstream kubernetes: kubernetes/kubernetes#48937 According to my understanding this will be fixed from 1.8 with the following patch: kubernetes/kubernetes#51634
In 1.7 release the shared PID namespaces is enabled by default. This is causing a problem when running pbench container which runs systemd. Related issue in upstream kubernetes: kubernetes/kubernetes#48937 According to my understanding this will be fixed from 1.8 with the following patch: kubernetes/kubernetes#51634
What this PR does / why we need it: Reverts to the previous docker default of using isolated PID namespaces for containers in a pod. There exist container images that expect always to be PID 1 which we want to support unmodified in 1.8.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #48937Special notes for your reviewer:
Release note: