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
Ubuntu: kube-up.sh failed #39224
Comments
I follow this page http://kubernetes.io/docs/getting-started-guides/ubuntu/manual/ install kubernetes on ubuntu. And got the same issue. |
I have same issue
during investigation i use kubernetes/cluster/ubuntu$ ./download-release.sh
second try was find and result was
at the end i find function which try to read k8s version from file in KUBE_ROOT when i create this file download working
|
Same issue here. I'm using the v1.5.2 tag version.
|
localhost ubuntu 16.10 The tutorial in question |
is there any workaround or fix is available for the same issue? |
I have found a fix. Not pretty but works DOWNLOAD_URL_PREFIX="${KUBERNETES_RELEASE_URL}/v${KUBERNETES_RELEASE}" there is a v missing in ${KUBERNETES_RELEASE} |
I have found that $KUBE_ROOT/version is missing. Added "v1.5.4" to version file then it worked. |
Try this #43215
…On Fri, Mar 17, 2017 at 1:36 PM, Tien Dinh ***@***.***> wrote:
Noone can help ? I got same issue
***@***.***:~/kubernetes/cluster# KUBERNETES_PROVIDER=ubuntu ./kube-up.sh
... Starting cluster using provider: ubuntu
... calling verify-prereqs
Identity added: /root/.ssh/id_rsa (/root/.ssh/id_rsa)
... calling verify-kube-binaries
!!! kubectl appears to be broken or missing
!!! Cannot find kubernetes-server-linux-amd64.tar.gz
!!! Cannot find kubernetes-salt.tar.gz
Required binaries appear to be missing. Do you wish to download them? [Y/n]
Can't determine Kubernetes release.
/root/kubernetes/cluster/get-kube-binaries.sh should only be run from a
prebuilt Kubernetes release.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#39224 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABloUvXLWiVHLdy6dx_QCgfrSXunrPWIks5rmj7-gaJpZM4LVWO8>
.
--
*{*
* "Regards" : {*
* "Name" : "Asif J.",*
* "Cell" : "+91 97385 47018",*
* "Github" : "asifhj",*
* "Skype" : "asif.h.j",*
* "LinkedIn" : "https://www.linkedin.com/in/asifhj
<https://www.linkedin.com/in/asifhj>"*
* }*
*}*
|
cc @resouer, @WIZARD-CXY |
Ah, I think I know what's wrong here. #38730 added a check ( This works fine if you run kube-up.sh from a kubernetes.tar.gz release tarball, but not if you clone the repo and try running The ubuntu provider does try to download the necessary binaries, but it does so in I'm not sure what the proper fix is. The ubuntu provider seems to stage the binaries in a different way than other providers. |
Yes, I was already switched to kubeadm, also the Anyway, I can user kubeadm and customized ansible script to install a fresh cluster, and think this issue is low priority for now. ;-) @WIZARD-CXY |
Maybe the correct fix is to update the docs to suggest using kubeadm instead of kube-up.sh? |
+1, an even more aggressive thinking is remove https://kubernetes.io/docs/getting-started-guides/ubuntu/manual/ , as this document was not maintained for a long time, the latest Kubernetes cannot work with this guidance. @ixdy |
Fine with me, though I'll leave it to the maintainers of that doc to decide. |
(Arguably if we delete that doc we should also delete the corresponding deprecated scripts in |
close this one as we are planning to deprecate those scripts. |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.):
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.):
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Kubernetes version (use
kubectl version
):Environment:
uname -a
):What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
The text was updated successfully, but these errors were encountered: