cAdvisor in 1.4 does not work on RHEL

[eparis]

see: google/cadvisor#1461

This issue is purely for tracking purposes.

[dchen1107]

Both @derekwaynecarr and I think this shouldn't be the blocker for 1.4 since it only impacts running cAdvisor or Kubelet in a container. I can be convinced though.

[four43]

This would break usage in CoreOS too, no? They have provisioning docs that run the Kubelet as a container with the rkt engine.

https://github.com/coreos/coreos-kubernetes

[dchen1107]

cc/ @philips @euank on CoreOS use case.

[philips]

cc @aaronlevy @pbx0

[philips]

@aaronlevy didn't see any failures in testing beta.8 but the way we run kubelet under rkt is different than I think the issue referred does cAdvisor in a docker container.

We will see if beta.9 turns anything up.

[aaronlevy]

This specific issue does not seem to affect CoreOS installs (tested beta.8 & beta.9).

[derekwaynecarr]

The fix was merged to cAdvisor

google/cadvisor#1476

On Wednesday, September 21, 2016, Aaron Levy notifications@github.com
wrote:

This specific issue does not seem to affect CoreOS installs (tested beta.8
& beta.9).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#32917 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF8dbFiLNGgYpLrmoli0hUzd7AlJLx20ks5qseSagaJpZM4J_aGa
.

[derekwaynecarr]

The backport into cAdvisor v0.24 is here: google/cadvisor#1478

[fejta-bot]

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close