-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
cri-dockerd: add restart of docker.service #9205
cri-dockerd: add restart of docker.service #9205
Conversation
Hi @krystianmlynek. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the 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. |
#9201 should have addressed this problem already, did you try the latest master and experienced the same issue? |
It fixes only kubelet failure after reboot, so I'll remove enabling of |
Thanks for the explanation @krystianmlynek /approve |
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.
/lgtm
Thanks for the explanation in the other PR
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cristicalin, floryut, krystianmlynek The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* upstream/master: (832 commits) add pre-commit hook to facilitate local testing (kubernetes-sigs#9158) cri-dockerd: add restart of docker.service (kubernetes-sigs#9205) do not run etcd role in scale.yml playbook when etcd installed by kubeadm (kubernetes-sigs#9210) optimize the format of evictionHard in kubelet-config.yaml template (kubernetes-sigs#9204) Update vars.md (kubernetes-sigs#9172) fix one bug in docs/nodes (kubernetes-sigs#9203) Fix containerd (<1.7) configuration for insecure registries (kubernetes-sigs#9207) 🌱 Enable cri-dockerd service (kubernetes-sigs#9201) Update vsphere-csi.md (kubernetes-sigs#9170) 9035: Make Cilium rolling-restart delay/timeout configurable (kubernetes-sigs#9176) [kubernetes] Add hashes for 1.24.4, 1.22.13, 1.23.10 and make v1.24.4 default (kubernetes-sigs#9191) Add 'avoid-buggy-ips' support of MetalLB (kubernetes-sigs#9166) Add the option to enable default Pod Security Configuration (kubernetes-sigs#9017) Add 'flush ip6tables' task in reset role (kubernetes-sigs#9168) add list nodes rules to cilium-operator clusterrole (kubernetes-sigs#9178) docs(kube-vip): fix broken links (kubernetes-sigs#9165) Disable DNSStubListener for Flatcar Linux (kubernetes-sigs#9160) Subnet setup order fix & Number of master nodes syntax fix (kubernetes-sigs#9159) Fix CSI drivers issues on Azure (kubernetes-sigs#9153) [calico] calico rr supports multiple groups (kubernetes-sigs#9134) ...
* cri-dockerd: add restart of docker.service * remove enabling of cri-dockerd.socket
* cri-dockerd: add restart of docker.service * remove enabling of cri-dockerd.socket
* cri-dockerd: add restart of docker.service * remove enabling of cri-dockerd.socket
* cri-dockerd: add restart of docker.service * remove enabling of cri-dockerd.socket
* cri-dockerd: add restart of docker.service * remove enabling of cri-dockerd.socket
* cri-dockerd: add restart of docker.service * remove enabling of cri-dockerd.socket
* cri-dockerd: add restart of docker.service * remove enabling of cri-dockerd.socket
What type of PR is this?
/kind bug
What this PR does / why we need it:
With this change docker will be restarted which will allow docker to pick up proxy/registry mirrors settings.
Which issue(s) this PR fixes:
Fixes #9142
Special notes for your reviewer:
Clone of PR #9174 since I got tired of trying to fix CI/merge conflicts
Does this PR introduce a user-facing change?: