Skip to content
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

ensure docker restart happens only once #8618

Closed
medyagh opened this issue Jul 1, 2020 · 1 comment · Fixed by #8621
Closed

ensure docker restart happens only once #8618

medyagh opened this issue Jul 1, 2020 · 1 comment · Fixed by #8621
Labels
area/guest-vm General configuration issues with the minikube guest VM area/performance Performance related issues co/runtime/docker Issues specific to a docker runtime priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@medyagh
Copy link
Member

medyagh commented Jul 1, 2020

on a KVM start log I saw docker restart happened twice during minikube start. which is slow

we should also add integration test ( by checking the logs ) to ensure that the docker restart happened only once (in functional test)

@afbjorklund
Copy link
Collaborator

afbjorklund commented Jul 1, 2020

I added a docker restart in #8518, when it had been started with the containerd service (about to be stopped)

Since we start every service at boot, before it is configured, we have to do a lot of cleanup like this. Would be nice to avoid that...

But we needed this restart, since otherwise docker was hanging waiting for /run/containerd/containerd.sock

Ultimately I would like to fix the ISO (so that it can be restarted), and move the init/systemd scripts out of minikube altogether.


But an interim fix would be to rewrite the current units, and make them more like the vendor packages ?

docker.service
● ├─containerd.service
● ├─docker.socket
● ├─system.slice
● ├─network-online.target
● │ ├─networking.service
● │ └─NetworkManager-wait-online.service
● └─sysinit.target

docker.service
● ├─docker.socket
● ├─minikube-automount.service
● ├─system.slice
● └─sysinit.target

It seems like something changed in the boot order, so now containerd is more likely to start before dockerd.

systemctl list-dependencies docker

systemd-analyze critical-chain docker.service

@afbjorklund afbjorklund added co/runtime/docker Issues specific to a docker runtime area/performance Performance related issues area/guest-vm General configuration issues with the minikube guest VM labels Jul 1, 2020
@afbjorklund afbjorklund added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/guest-vm General configuration issues with the minikube guest VM area/performance Performance related issues co/runtime/docker Issues specific to a docker runtime priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants