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

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

Open
premkritin opened this issue May 30, 2020 · 6 comments
Labels
co/none-driver kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-solution-message Issues where where offering a solution for an error would be helpful os/linux priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@premkritin
Copy link

premkritin commented May 30, 2020

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
Copy link
Collaborator

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 afbjorklund added co/none-driver kind/support Categorizes issue or PR as a support question. os/linux labels May 30, 2020
@afbjorklund
Copy link
Collaborator

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 afbjorklund added the needs-solution-message Issues where where offering a solution for an error would be helpful label May 30, 2020
@afbjorklund
Copy link
Collaborator

afbjorklund commented May 30, 2020

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

@medyagh medyagh changed the title unable to start minikube The "openrc" sysinit should probably verify that it is actually using OpenRC Jul 15, 2020
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 13, 2020
@sharifelgamal sharifelgamal added kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed kind/support Categorizes issue or PR as a support question. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 11, 2020
@fejta-bot
Copy link

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-contributor-experience at kubernetes/community.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 9, 2021
@sharifelgamal sharifelgamal added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 18, 2021
@sharifelgamal
Copy link
Collaborator

Still an issue, I suspect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/none-driver kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-solution-message Issues where where offering a solution for an error would be helpful os/linux priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

5 participants