Provide PSR information for containers.

[mJace]

Allow cadvisor to provide PSR information when doing ps to containers now.
PSR is a ps output option, it shows which cpu that current process runs on.

The related issue:
#2290

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[k8s-ci-robot]

Hi @mJace. Thanks for your PR.

I'm waiting for a google or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[mJace]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[dashpole]

/ok-to-test

[dashpole]

/retest

[mJace]

@dashpole How do I run the test in my fork?
I tried to make test at /cadvisor when I just fork master and without changing any code but it has some failure.

[dashpole]

++ git diff --name-only pages
W0816 19:01:14.397] + [[ ! -z pages/static/assets.go ]]
W0816 19:01:14.398] + echo 'Found changes to UI assets:'
W0816 19:01:14.398] + git diff --name-only pages
W0816 19:01:14.405] ++ make assets FORCE=true
I0816 19:01:14.507] Found changes to UI assets:
I0816 19:01:14.508] pages/static/assets.go
I0816 19:01:15.332] Run: >> building assets
W0816 19:01:15.434] + echo 'Run: >> building assets'
W0816 19:01:15.434] + exit 1

Try just running make locally to reproduce the failure.

[mJace]

@dashpole Sorry, I have some problem reproducing the make failure.

I have this error when running make in my master and numa_support branch
log.txt
My master is same as latest google/cadvisor
d200c9f

But if I manually copy 3 modified files to my local google/master and run make.
It can run successfully.
logSuccess.txt

[dashpole]

ah, apologies. I forgot about some changes we made to scripts a while back.
You will need to run make assets FORCE=true.

It looks like there is a bug with the script that actually runs make assets FORCE=true, rather than printing it: https://github.com/google/cadvisor/blob/master/build/prow_e2e.sh#L34

I opened #2296 to fix the print statement.

[mJace]

@dashpole
Thanks for your fix.
Should I wait for the #2296 to merged to master and re-create this PR again?

Cuz, I still have trouble to run make at my own fork, even if I change the prow_e2e.sh as #2296 did.
But just like I said if I run make at google/cadvisor with the 3 modified file, it can pass the make

But it seems like they are 2 different problems?
#2296 is for pull-cadvisor-e2e CI fail.
the make fail at my on fork is another story.

[dashpole]

Yeah, you are correct. To fix the failure here, run make assets FORCE=true to rebuild UI assets, and commit the changes.

My PR just fixes the error message from #2291 (comment) so it tells you how to fix that problem.

[mJace]

Yeah, you are correct. To fix the failure here, run make assets FORCE=true to rebuild UI assets, and commit the changes.

My PR just fixes the error message from #2291 (comment) so it tells you how to fix that problem.

I see, thank you.

[dashpole]

lgtm

[dashpole]

sorry, if you can rebase this, i'm happy to merge it.

[mJace]

@dashpole Thank you!
But I have a build error on the latest master branch 425e211

make build
>> building assets
>> building binaries
>> building cadvisor
internal/storage/influxdb/influxdb.go:29:2: cannot find package "github.com/influxdb/influxdb/client" in any of:
	/usr/local/go/src/github.com/influxdb/influxdb/client (from $GOROOT)
	/home/jace/go/src/github.com/influxdb/influxdb/client (from $GOPATH)
make: *** [Makefile:70: build] Error 1

Can you check this for me? I tried go v1.11 v1.12 v1.13

Or can I ignore the build error on latest master branch, just rebase my branch on google:master ?
Since I can still generate the assets though

[dashpole]

I would just rebase on master. If it has problems, you can check the logs from the presubmits if you can't get it working in your dev env. I think we use go 1.14 now btw

[mJace]

@dashpole I rebased my branch. Could you take a look? thank you!