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

start_stop_with_containerd_runtime: Job for docker.service failed because the control process exited with error code. #3424

Closed
tstromberg opened this issue Dec 6, 2018 · 0 comments
Labels
kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@tstromberg
Copy link
Contributor

Seen at go/bugbear/logs/OSX_Integration_Tests_VirtualBox/builds/3322?hash=t=6hMUD,kctl=ojkdi,mk=m2FJz

--- FAIL: TestStartStop (773.58s)
--- PASS: TestStartStop/default (269.78s)
--- FAIL: TestStartStop/start_stop_with_containerd_runtime (503.80s)
util.go:78: Error running command: start --vm-driver=virtualbox --v=10 --logtostderr --bootstrapper=kubeadm --container-runtime=containerd --network-plugin=cni --docker-opt containerd=/var/run/containerd/containerd.sock I1205 14:15:32.868229 11620 notify.go:121] Checking for updates...
I1205 14:15:33.243111 11620 start.go:100] Viper configuration:
...
# the command from the base configuration and the command specified here are treated as
# a sequence of commands, which is not the desired behavior, nor is it valid -- systemd
# will catch this invalid input and refuse to start the service with an error like:
# Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services.
...
# the command from the base configuration and the command specified here are treated as
# a sequence of commands, which is not the desired behavior, nor is it valid -- systemd
# will catch this invalid input and refuse to start the service with an error like:
# Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services.
...
&{{{<nil> 0 [] [] []} docker [0x140f940] 0x140f910 [] 0s} 127.0.0.1 50689 <nil> <nil>}
About to run SSH command:
sudo systemctl -f restart docker
SSH cmd err, output: Process exited with status 1: Job for docker.service failed because the control process exited with error code.

Logs show:

Dec 05 22:16:24 minikube systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Dec 05 22:16:24 minikube systemd[1]: docker.service: Failed with result 'exit-code'.
Dec 05 22:16:24 minikube systemd[1]: Failed to start Docker Application Container Engine.
@tstromberg tstromberg added the kind/flake Categorizes issue or PR as related to a flaky test. label Dec 6, 2018
@tstromberg tstromberg changed the title start_stop_with_containerd_runtime: start_stop_with_containerd_runtime: Job for docker.service failed because the control process exited with error code. Dec 6, 2018
priyawadhwa pushed a commit to priyawadhwa/minikube that referenced this issue Dec 7, 2018
Only allow the buildroot provisioner to restart docker if the container
runtime is docker. This change should fix the bug in kubernetes#3424, since now
docker will not be restarted if the container runtime is containerd.
balopat pushed a commit that referenced this issue Dec 7, 2018
* Only restart docker service if container runtime is docker

Only allow the buildroot provisioner to restart docker if the container
runtime is docker. This change should fix the bug in #3424, since now
docker will not be restarted if the container runtime is containerd.

* Added files to fix FileContent--proc-sys-net-bridge-bridge-nf-call-iptables precheck error

From this issue: kubernetes/kubeadm#1062
these files need to be added to prevent this precheck error (which occurs when running any container runtime that isn't docker).

Also, save the machine config on the user's filesystem earlier so that the buildprovisioner can access it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Development

No branches or pull requests

1 participant