Closed ucohen closed 3 years ago
tstromberg
commented
3 years ago Instead of using docker-env, which only Docker respects, set the environment variable so that the Go program (minikube) can respect it as well. Try:
HTTPS_PROXY=http://proxy-iil.intel.com:912 \
NO_PROXY=localhost,127.0.0.1,10.96.0.0/12,192.168.99.0/24,192.168.39.0/24,192.168.49.0/24,192.168.99.100/24 \
minikube start --driver=docker`
You can also set these variables permanently in your shell environment.Please let me know if this helps!
ucohen
commented
3 years ago Thanks for your reply @tstromberg I think there is a progress, now I have get error for non-existing directory, could you have a look?
stderr:
ls: cannot access '/etc/kubernetes/admin.conf': No such file or directory
ls: cannot access '/etc/kubernetes/kubelet.conf': No such file or directory
...full log:
tstromberg
commented
3 years ago Looks like we don't know how to handle certificate file names containing parentheses.
On Sun, Dec 13, 2020, 5:23 AM ucohen notifications@github.com wrote:
Thanks for your reply @tstromberg https://github.com/tstromberg I think there is a progress, now I have a certificate parsing issue, could you have a look?
➜ minikube start --driver=docker
😄 minikube v1.15.1 on Ubuntu 18.04
✨ Using the docker driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🔥 Creating docker container (CPUs=2, Memory=32100MB) ...
✋ Stopping node "minikube" ...
🛑 Powering off "minikube" via SSH ...
🔥 Deleting "minikube" in docker ...
🤦 StartHost failed, but will try again: post-start: sudo test -d /etc/ssl/certs && sudo scp -t /etc/ssl/certs && sudo touch -d "2018-08-22 09:34:44 +0300" /etc/ssl/certs/IntelCA5A(1)-base64.crt: Process exite$
with status 1
output: bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `sudo test -d /etc/ssl/certs && sudo scp -t /etc/ssl/certs && sudo touch -d "2018-08-22 09:34:44 +0300" /etc/ssl/certs/IntelCA5A(1)-base64.crt'
🔥 Creating docker container (CPUs=2, Memory=32100MB) ...
😿 Failed to start docker container. Running "minikube delete" may fix it: post-start: sudo test -d /etc/ssl/certs && sudo scp -t /etc/ssl/certs && sudo touch -d "2018-08-22 09:34:44 +0300" /etc/ssl/certs/Inte$
CA5A(1)-base64.crt: Process exited with status 1
output: bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `sudo test -d /etc/ssl/certs && sudo scp -t /etc/ssl/certs && sudo touch -d "2018-08-22 09:34:44 +0300" /etc/ssl/certs/IntelCA5A(1)-base64.crt'
❌ Exiting due to GUEST_PROVISION: Failed to start host: post-start: sudo test -d /etc/ssl/certs && sudo scp -t /etc/ssl/certs && sudo touch -d "2018-08-22 09:34:44 +0300" /etc/ssl/certs/IntelCA5A(1)-base64.cr$
: Process exited with status 1
output: bash: -c: line 0: syntax error near unexpected token `('
bash: -c: line 0: `sudo test -d /etc/ssl/certs && sudo scp -t /etc/ssl/certs && sudo touch -d "2018-08-22 09:34:44 +0300" /etc/ssl/certs/IntelCA5A(1)-base64.crt'
😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/minikube/issues/9874#issuecomment-744007081, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAYYMDMJ6JDBY5QQQLNVULSUS53TANCNFSM4UQVKR2Q .
ucohen
commented
3 years ago Looks like we don't know how to handle certificate file names containing parentheses.
I figured this was the issue so I've updated the certificate name and got this error:
stderr:
ls: cannot access '/etc/kubernetes/admin.conf': No such file or directory
ls: cannot access '/etc/kubernetes/kubelet.conf': No such file or directory
...That particular error is benign. I suggest running minikube delete to cleanup the existing state, and then run minikube start -- please let me know what the final 5 lines of output end up being if it fails then.
ucohen
commented
3 years ago @tstromberg here is the output I get
minikube start --driver docker
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 17.503121 seconds
[upload-config] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-1.19" in namespace kube-system with the configuration for the kubelets in the cluster
[kubelet-check] Initial timeout of 40s passed.
stderr:
W1214 19:34:51.075228 868 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[WARNING Swap]: running with swap on is not supported. Please disable swap
[WARNING SystemVerification]: failed to parse kernel config: unable to load kernel module: "configs", output: "modprobe: FATAL: Module configs not found in directory /lib/modules/5.4.0-56-generic\n", err: exit status 1
[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
error execution phase upload-config/kubelet: Error writing Crisocket information for the control-plane node: timed out waiting for the condition
To see the stack trace of this error execute with --v=5 or higher
medyagh
commented
3 years ago @ucohen I am curious if you have already tried to sign the minikube cert with your corp cert ?
medyagh
commented
3 years ago @ucohen I haven't heard from you, do you still have this issue ?
spowelljr
commented
3 years ago Hi @ucohen, we haven't heard back from you, do you still have this issue? There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.
I will close this issue for now but feel free to reopen when you feel ready to provide more information.
Trying to start minikube behind corporate proxy, I cannot get it to start. I trid to folow https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy - not sure if got it correct.
Steps to reproduce the issue:
Full output of
minikube startcommand used, if not already included:Optional: Full output of
minikube logscommand: