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.

Sign up for GitHub

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

Jump to bottom

none: Add support for non-systemd Linux distributions #2704

Closed
andyxning opened this issue Apr 11, 2018 · 30 comments
Closed

none: Add support for non-systemd Linux distributions #2704

andyxning opened this issue Apr 11, 2018 · 30 comments
Labels
co/kubeadm Issues relating to kubeadm co/kubelet Kubelet config issues co/none-driver good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. 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. os/linux priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@andyxning
Copy link
Member

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
@asymmetric
Copy link

asymmetric commented Apr 11, 2018 •
edited
Loading

The same thing is happening on CircleCI.

It seems to be due to minikube expecting to find systemctl, which is not there on the CircleCi Ubuntu Trusty box at least (and I suspect on the Travis boxes either).

@asymmetric asymmetric mentioned this issue Apr 11, 2018
Merged
@dlorenc
Copy link
Contributor

dlorenc commented Apr 11, 2018

I think you'll need to pass --bootstrapper=localkube to work with the none driver in environments that don't have system for now.

@andyxning
Copy link
Member Author

@dlorenc Is this the recommended way to work around systemd or this is a regression bug?

@dlorenc
Copy link
Contributor

dlorenc commented Apr 11, 2018

It's a bit of a regression caused by the switch from localkube to kubeadm by default. Kubeadm with the none driver requires systemd.

The other problem here is that travis only supports up to Ubuntu 14.04, and systemd was added in 16.04.

@andyxning
Copy link
Member Author

/cc @r2d4

@andyxning
Copy link
Member Author

/cc @aaron-prindle

asymmetric added a commit to kinvolk-archives/habitat-operator that referenced this issue Apr 11, 2018
@asymmetric
ci: Force minikube to use localkube
0022b23 
The default is `kubeadm`, which requires systemd, which is not present
on Trusty, which is what's used by both CircleCI and Travis.

This change should be reverted once this issue is fixed: kubernetes/minikube#2704
@andyxning
Copy link
Member Author

andyxning commented Apr 11, 2018 •
edited
Loading

@dlorenc seems we force use --bootstrapper=localkube is fine and it is ok even travis later bump Ubuntu from 14.04 to 16.04 if we have no strong dependency on kubeadm features. Or should minikube fix the compatibility problem.

@andyxning andyxning mentioned this issue Apr 11, 2018
Closed
earlgreyz added a commit to grtl/mysql-operator that referenced this issue Apr 12, 2018
@earlgreyz
Fix minikube not starting on Travis-CI
6855d27 
kubernetes/minikube#2704
@earlgreyz earlgreyz mentioned this issue Apr 12, 2018
Merged
earlgreyz added a commit to grtl/mysql-operator that referenced this issue Apr 12, 2018
@earlgreyz
Fix minikube not starting on Travis-CI
a53a799 
kubernetes/minikube#2704
This was referenced Apr 12, 2018
Closed
Closed
Closed
@fabiand
Copy link
Contributor

fabiand commented Apr 12, 2018

We are also experiencing this.

It sounds like travis will need some time to provide an image with systemd.
Thus I wonder if minikube could at least do a check if systemd is present, to output a warning if the kubeadm bootstrapper is used.

This would at least highlight the problem.

I am not sure what the right fix is tho (wait for travis update or fix it in minikube).

fabiand added a commit to fabiand/kubevirt-demo that referenced this issue Apr 12, 2018
@fabiand
travis: Pin to specific minikube version
437b5c2 
Workaround for kubernetes/minikube#2704

Resolves: kubevirt#42

Signed-off-by: Fabian Deutsch <[email protected]>
fabiand added a commit to fabiand/kubevirt-demo that referenced this issue Apr 12, 2018
@fabiand
travis: Pin to specific minikube version
ab4c695 
Workaround for kubernetes/minikube#2704

Resolves: kubevirt#42

Signed-off-by: Fabian Deutsch <[email protected]>
@fabiand fabiand mentioned this issue Apr 12, 2018
Merged
@gkganesh126 gkganesh126 mentioned this issue Apr 12, 2018
Merged
@djzager djzager mentioned this issue Apr 12, 2018
Merged
@andyxning
Copy link
Member Author

@dlorenc @r2d4 @aaron-prindle

tombentley added a commit to strimzi/strimzi-kafka-operator that referenced this issue Apr 17, 2018
@tombentley
Use localkube not kubeadm
2358f37 
See kubernetes/minikube#2704 (comment)
@CelineBoudier CelineBoudier mentioned this issue Apr 19, 2018
Closed
@dgrove-oss dgrove-oss mentioned this issue Apr 19, 2018
Closed
@afbjorklund afbjorklund mentioned this issue Apr 20, 2018
Closed
2 tasks
@slok slok mentioned this issue Apr 21, 2018
Merged
@andyxning
Copy link
Member Author

Ping @dlorenc @r2d4 @aaron-prindle Any suggestions? Pinning on an old version of minikube is not so good from a long run perspective.

@andyxning
Copy link
Member Author

Friendly ping.~

@afbjorklund afbjorklund mentioned this issue May 7, 2019
Closed
@tstromberg tstromberg reopened this May 14, 2019
@tstromberg tstromberg added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. kind/feature Categorizes issue or PR as related to a new feature. and removed kind/bug Categorizes issue or PR as related to a bug. labels May 14, 2019
@tstromberg tstromberg changed the title None driver requires systemd due to kubeadm dependency (systemctl: exit status 1) none: Add support for non-systemd Linux distributions May 14, 2019
@tstromberg tstromberg mentioned this issue May 15, 2019
Merged
foot added a commit to weaveworks/launcher that referenced this issue Jun 24, 2019
@foot
Internet suggested hack to get minikube+circleci
122583d 
kubernetes/minikube#2704 (comment)
foot added a commit to weaveworks/launcher that referenced this issue Jun 25, 2019
@foot
Test multiple versions of k8s (#291)
baf30e1 
* Test multiple versions of k8s
* Internet suggested hack to get minikube+circleci
kubernetes/minikube#2704 (comment)
* Add a third "stable" target for k8s testing
* Re-run kubernetes jobs once a day in case of new k8s
@tstromberg tstromberg mentioned this issue Sep 12, 2019
Closed
@sharifelgamal
Copy link
Collaborator

/reopen

@k8s-ci-robot
Copy link
Contributor

@sharifelgamal: Reopened this issue.

In response to this:

/reopen

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.

@k8s-ci-robot k8s-ci-robot reopened this Sep 20, 2019
@codebling
Copy link

The switch suggested above did not work for me on minikube 1.4.0.
As a quick fix if you're not running systemd,

sudo touch /usr/bin/systemctl
sudo chmod a+r /usr/bin/systemctl

It's just an empty script, which only works because it returns a non-zero exit code, effectively bypassing the attempt to start dockerd. You'll need to manually start dockerd first.

I gave up on what I was trying when I ran into more issues but it got me past that hurdle

@medyagh
Copy link
Member

medyagh commented Dec 16, 2019

this is still a feature that havent been implemented

not same but related in a way #4172

@medyagh
Copy link
Member

medyagh commented Mar 8, 2020

related #6954

we still need to do this ! anyone interested ?

@medyagh medyagh added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. long-term-support Long-term support issues that can't be fixed in code priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed long-term-support Long-term support issues that can't be fixed in code priority/backlog Higher priority than priority/awaiting-more-evidence. labels Mar 8, 2020
@afbjorklund afbjorklund mentioned this issue Mar 15, 2020
Closed
@amitkrout amitkrout mentioned this issue Apr 2, 2020
Closed
@prietyc123
Copy link

We need to pass --bootstrapper=localkube to work with the none driver in environments to start minikube like minikube start --vm-driver=none --bootstrapper=localkube --kubernetes-version=v1.10.0 . While doing this it should be kept in mind that we are using the older version of minikube which comes before v0.26+ and kubernetes version which support --bootstrapper=localkube .

@afbjorklund
Copy link
Collaborator

Support for localkube and v1.10.0 has been suspended (in 2018), suggest looking at k3s if you want something similar for modern kubernetes versions. Minikube now uses kubeadm and v1.18.0.

@afbjorklund afbjorklund mentioned this issue May 10, 2020
Open
@afbjorklund afbjorklund mentioned this issue Jun 26, 2020
Closed
@tstromberg
Copy link
Contributor

We fixed this by adding support for OpenRC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
co/kubeadm Issues relating to kubeadm co/kubelet Kubelet config issues co/none-driver good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. 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. os/linux priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests