-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix renaming of "runtime" container to "docker-daemon" #1656
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
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. |
Hi @loburm. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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. |
|
Please provide a more detailed description in both the commit body and the PR description. Please try also to not have too long of a commit message title (otherwise it wraps). |
Thanks for the comments, I have updated PR description and commit title. |
/lgtm |
@k8s-bot ok to test |
This PR fix #1639. Previously all containers named "runtime" have been renamed to "docker-daemon" (that's because reverse procedure was done in kubernetes). Now we are renaming to "docker-daemon" only system containers to avoid cases when container which was originally named as "runtime" renamed to "docker-daemon".