minishift Failed with FAIL E0512 00:52:28.241953 14348 start.go:494] Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host #3258
Comments
|
I am not really following your instructions. So you are using proxy? So,
where is that information provided? did you manually download/copy files?
If so, why?!?? did the connection fail to download? if so, this sounds like
a general issue with your networking setup (minishift does support proxy).
|
|
Hi
Hi , While running the oracle virtualbox , minishift trying to provision docker instance, so its failing at that stage, i moved to Hyper-V and able to create vm in Hyper-V but this is error i'm getting C:\minishift> .\minishift start --show-libmachine-logs --v=5 CENTOS_MANTISBT_PROJECT="CentOS-7" VARIANT="minishift" Detecting the provisioner... Setting hostname ... |
|
this error is usually caused when you have a n existing VM that changed IP
address. Try removing this VM and use a start that starts a clean instance.
…On Sun, May 12, 2019, 03:55 PraveenBommali ***@***.***> wrote:
General information
- Minishift version:
- OS: Windows
- Hypervisor: VirtualBox
Steps to reproduce
1. Running under proxy, due to issue download manually oc.exe and
minishift-centos7.iso and placed in C:\Users\User.minishift\cache
2. started minishift by
C:\minishift>minishift start
Expected
Vm need to be created in VirtualBox - created successfully
Able to launch the minishift from browser
Actual
Vm need to be created in VirtualBox - created successfully
Getting error
Logs
vCPUs : 2
Disk size: 20 GB
-- Starting Minishift VM
.................................................... FAIL E0512
01:04:59.774751 14708 start.go:494] Error starting the VM: Error creating
the VM. Error creating machine: Error checking the host: Error checking
and/or regenerating the certs: There was an error validating certificates
for host "192.168.99.103:2376": dial tcp 192.168.99.103:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs
[name]'.
Be advised that this will trigger a Docker daemon restart which might stop
running containers.
. Retrying.
Error starting the VM: Error creating the VM. Error creating machine:
Error checking the host: Error checking and/or regenerating the certs:
There was an error validating certificates for host "192.168.99.103:2376":
dial tcp 192.168.99.103:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs
[name]'.
Be advised that this will trigger a Docker daemon restart which might stop
running containers.
You can start Minishift with minishift start --show-libmachine-logs -v5
to collect logs.
Please consider posting this on http://gist.github.com/ and post the link
in the issue.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3258>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAAOZVAH6Z2XCALYWIT633PU4QCTANCNFSM4HMI4CAQ>
.
|
Hi, I tried in that way lot of times, still failing some time , out of memory issue, even i have enough memory , |
|
Please provide more info. How much memory do you assign ?
have you removed the instance with:
```
$ minishift delete -f --clear-cache
```
Make sure you run a new instance.
On Wed, May 15, 2019 at 9:12 AM PraveenBommali <notifications@github.com>
wrote:
… this error is usually caused when you have a n existing VM that changed IP
address. Try removing this VM and use a start that starts a clean instance.
… <#m_5799996540532309987_>
On Sun, May 12, 2019, 03:55 PraveenBommali *@*.***> wrote: General
information - Minishift version: - OS: Windows - Hypervisor: VirtualBox
Steps to reproduce 1. Running under proxy, due to issue download manually
oc.exe and minishift-centos7.iso and placed in
C:\Users\User.minishift\cache 2. started minishift by
C:\minishift>minishift start Expected Vm need to be created in VirtualBox -
created successfully Able to launch the minishift from browser Actual Vm
need to be created in VirtualBox - created successfully Getting error Logs
vCPUs : 2 Disk size: 20 GB -- Starting Minishift VM
.................................................... FAIL E0512
01:04:59.774751 14708 start.go:494] Error starting the VM: Error creating
the VM. Error creating machine: Error checking the host: Error checking
and/or regenerating the certs: There was an error validating certificates
for host "192.168.99.103:2376": dial tcp 192.168.99.103:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs
[name]'. Be advised that this will trigger a Docker daemon restart which
might stop running containers. . Retrying. Error starting the VM: Error
creating the VM. Error creating machine: Error checking the host: Error
checking and/or regenerating the certs: There was an error validating
certificates for host "192.168.99.103:2376": dial tcp 192.168.99.103:2376:
i/o timeout You can attempt to regenerate them using 'docker-machine
regenerate-certs [name]'. Be advised that this will trigger a Docker daemon
restart which might stop running containers. You can start Minishift with
minishift start --show-libmachine-logs -v5 to collect logs. Please consider
posting this on http://gist.github.com/ and post the link in the issue. —
You are receiving this because you are subscribed to this thread. Reply to
this email directly, view it on GitHub <#3258
<#3258>>, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAAOZVAH6Z2XCALYWIT633PU4QCTANCNFSM4HMI4CAQ
.
Hi, I tried in that way lot of times, still failing some time , out of
memory issue, even i have enough memory ,
or i'm getting tcp disconnect error ,
can you please me out, how to run the with static ip , under proxy network
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3258?email_source=notifications&email_token=AAAAOZSJWD5KWSCNBX4Q6PDPVNPP5A5CNFSM4HMI4CA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVNHC4Q#issuecomment-492466546>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAAOZSXNHN5WNTDWKJZR63PVNPP5ANCNFSM4HMI4CAQ>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Still this issue was remains in my local , I'm not sure, reason, I tried all options mentioned above but , i think the issue with I'm running under proxy with windows 10 . Same setup i ran in macos ,I'm able to succeed and launch the application. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
General information
Steps to reproduce
C:\minishift>minishift start
Expected
Vm need to be created in VirtualBox - created successfully
Able to launch the minishift from browser
Actual
Vm need to be created in VirtualBox - created successfully
Getting error
Logs
vCPUs : 2
Disk size: 20 GB
-- Starting Minishift VM .................................................... FAIL E0512 01:04:59.774751 14708 start.go:494] Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.103:2376": dial tcp 192.168.99.103:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.
. Retrying.
Error starting the VM: Error creating the VM. Error creating machine: Error checking the host: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.99.103:2376": dial tcp 192.168.99.103:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.
You can start Minishift with
minishift start --show-libmachine-logs -v5to collect logs.Please consider posting this on http://gist.github.com/ and post the link in the issue.
The text was updated successfully, but these errors were encountered: