The "openrc" sysinit should probably verify that it is actually using OpenRC

[premkritin]

minikube start

• minikube v1.11.0 on Amazon 2018.03 (xen/amd64)
• Using the none driver based on existing profile
• Starting control plane node minikube in cluster minikube
• Restarting existing none bare metal machine for "minikube" ...
• OS release is Amazon Linux AMI 2018.03
• Preparing Kubernetes v1.18.3 on Docker 19.03.6-ce ...

X Failed to update cluster: updating node: sudo service kubelet start: exit status 127
stdout:

stderr:
/etc/init.d/kubelet: line 9: start-stop-daemon: command not found

• minikube is exiting due to an error. If the above message is not useful, open an issue:

[afbjorklund]

Currently minikube has files for systemd and for openrc, if you use something else it needs adding.

https://www.freedesktop.org/software/systemd/man/systemd.unit.html

It is normally provided by "dpkg" on Ubuntu, you might have it somewhere else (for use by "service")

https://wiki.alpinelinux.org/wiki/Writing_Init_Scripts

[afbjorklund]

Apparently the old Amazon Linux does not use systemd, but the older CentOS system.

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/amazon-linux-ami-basics.html

There is no support in minikube for this, but I suppose it could be added (next to openrc).

Or you could upgrade to Amazon Linux 2 ? https://aws.amazon.com/amazon-linux-2/

[afbjorklund]

The "openrc" sysinit should probably verify that it is actually using OpenRC

For instance the start-stop-daemon is not portable, the way that "service" is

I believe it was called just daemon

But it was like decades ago, as well

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale