--vm-driver: none: Unable to customize APIServerPort

[mr-c]

Environment:

Installing minikube with --vm-driver=none on a system with existing use of port 8443 (Jenkins, in this case)

minikube version: v0.26.1

OS:
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

VM driver:
"DriverName": "none",

What happened:

minikube start --vm-driver=none --extra-config=kubelet.bindPort=9443                                                                        
Starting local Kubernetes v1.10.0 cluster...                                                                                                           
Starting VM...                                                                                                                                         
Getting VM IP address...                                                                                                                               
Moving files into cluster...                                                                                                                          
Setting up certs...                                                                                                                                    
Connecting to cluster...                                                                                                                               
Setting up kubeconfig...                                                                                                                               
Starting cluster components...                                                                                                                         
E0430 08:20:23.901698   15184 start.go:276] Error starting cluster:  kubeadm init error sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ign
ore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--etc-k
ubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors
=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ign
ore-preflight-errors=Swap --ignore-preflight-errors=CRI  running command: : running command: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml
--ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data --ignore-preflight-errors=FileAvailable--
etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-e
rrors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml
--ignore-preflight-errors=Swap --ignore-preflight-errors=CRI
 output: [init] Using Kubernetes version: v1.10.0
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
        [WARNING SystemVerification]: docker version is greater than the most recently validated version. Docker version: 18.03.0-ce. Max validated ver
sion: 17.03
        [WARNING Hostname]: hostname "minikube" could not be reached
        [WARNING Hostname]: hostname "minikube" lookup minikube on 173.203.4.9:53: no such host
        [WARNING FileExisting-crictl]: crictl not found in system path
Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl
Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future versio
n.
[preflight] Some fatal errors occurred:
        [ERROR Port-8443]: Port 8443 is in use

What you expected to happen:

To have a configuration option for APIServerPort

Thanks!

[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

[mr-c]

/remove-lifecycle stale

[sebcworks]

Had the same problem (something already listening to this port).

I made a fix and I'm actually testing it, if it is correct, I'll try to see if I can make a PR...

[hvantran]

Any update on this ticket. I am facing the same issue.

[simplyviks]

Had the same problem (something already listening to this port).

I made a fix and I'm actually testing it, if it is correct, I'll try to see if I can make a PR...

@sebcworks Many thanks for the enhancement ! when are you planning to merge this?

[sebcworks]

@simplyviks Thanks for your interest in my PR, meanwhile, I can't do any merge action myself!

We just have to wait for approvers to have time to do a full review/test of my changes.