-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update gvisor runsc version #4494
Update gvisor runsc version #4494
Conversation
Welcome @ianlewis! |
Can one of the admins verify this patch? |
1bce451
to
07b842a
Compare
/assign @sharifelgamal |
cc @medyagh |
Currently using anything newer than the 2019-01-14 version of runsc is blocked by #3512 because runsc uses pivot_root on newer versions. |
Also cc @priyawadhwa since she did the original gvisor addon. |
@minikube-bot OK to test |
/retest this please |
These Jenkins test failures don't seem to be related to this change. Not sure if there's any action I can take. |
/retest this please |
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.
Took a quick look and this makes sense to me! Could you also add runtimeClassName: gvisor
to nginx-untrusted.yaml to test this in the integration tests?
@minikube-bot OK to test |
It's probably a flake, but some of the gvisor tests failed:
|
@minikube-bot OK to test |
/retest this please |
@ianlewis the integration test fail for gvisor consistently on different platforms.
|
@medyagh I missed the tests, thanks for pointing them out. I modified the test data and added new tests, but I still can't get the tests to pass locally. Since the gVisor addon was modified I need the integration tests to use my updated version of the gvisor-addon image but I can't find a way to do that. I guess I should push all the images to my own repo and load from there? |
07b842a
to
f641bcc
Compare
@minikube-bot OK to test |
/retest this please |
New changes are detected. LGTM label has been removed. |
Travis tests have failedHey @ianlewis, 1st Buildmake test
TravisBuddy Request Identifier: 2d5acd10-c774-11e9-854a-5595b23fa18a |
cc42069
to
594e99e
Compare
Travis tests have failedHey @ianlewis, 1st Buildmake test
TravisBuddy Request Identifier: 0b9e9880-c7b2-11e9-854a-5595b23fa18a |
594e99e
to
f856177
Compare
Travis tests have failedHey @ianlewis, 1st Buildmake test
TravisBuddy Request Identifier: 8cbf6e20-c7b3-11e9-854a-5595b23fa18a |
f856177
to
e217128
Compare
Travis tests have failedHey @ianlewis, 1st Buildmake test
TravisBuddy Request Identifier: b704c400-c7bd-11e9-854a-5595b23fa18a |
|
- Updates the gvisor addon to use containerd shim v2 - Updates the version of runsc - Auto-installs a gvisor RuntimeClass Issue kubernetes#4482
e217128
to
d14bdbc
Compare
Yeah, I wasn't pushing the changes I thought I was pushing. |
The failing tests all seem to be failing in different ways and look like it may be flakes, but I can't tell. They don't seem to me to be related to my changes. |
/retest please |
@minikube-bot OK to test |
Containerd tests seem to be failing.... will take a look. |
I'm finding the integration tests to be pretty flaky when run in parallel. Opened #5255 |
@tstromberg |
Issue #4482