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

v1.10.3 with vagrant #64561

Closed
duke66 opened this issue May 31, 2018 · 4 comments
Closed

v1.10.3 with vagrant #64561

duke66 opened this issue May 31, 2018 · 4 comments
Assignees
@dims
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.

Comments

@duke66
Copy link

duke66 commented May 31, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
I am try to install kubernetes in vagrant local at macbook:
download https://github.com/kubernetes/kubernetes/releases/tag/v1.10.3 this and try to run:
KUBERNETES_PROVIDER=vagrant kubernetes/cluster/kube-up.sh

i got error with verify-kube-binaries:
"... Starting cluster using provider: vagrant
... calling verify-prereqs
Skeleton Provider: verify-prereqs not implemented
... calling verify-kube-binaries
./cluster/kube-up.sh: line 65: verify-kube-binaries: command not found"

Also i got this problem with run:
"export KUBERNETES_PROVIDER=vagrant
curl -sS https://get.k8s.io | bash"

After that i`m try run v1.9.8 and got success with same command.

What you expected to happen:
Run k8s local in vagrant

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
    v1.10.3
  • Cloud provider or hardware configuration:
    MacBook pro
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@k8s-ci-robot
Copy link
Contributor

@duke66: There are no sig labels on this issue. Please add a sig label.

A sig label can be added by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

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 added needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. kind/bug Categorizes issue or PR as related to a bug. labels May 31, 2018
@abdennour
Copy link

I have the same environment and I am facing the same issue.

BTW, I go to vagrant and I left minikube because its connection keeps losing since the last upgrade ( 1.10)/

@abdennour
Copy link

After a deep dive into the code of this repository, I realized that verify-kube-binaries is missing function which currently exists in ./cluster/common.sh.

solution:

# combine two scripts in one
cat cluster/common.sh cluster/kube-up.sh > cluster/kube-up-fixed.sh

# grant exec permission for the user owner
chmod u+x ./cluster/kube-up-fixed.sh

#Enjoy
chmod +x ./cluster/kube-up-fixed.sh

@dims
Copy link
Member

dims commented Jun 4, 2018

@abdennour thanks. Looks like we removed support for vagrant in 1.10, so closing this issue.

#58118

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dims dims

Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dims @abdennour @duke66 @k8s-ci-robot