I minishift myself this weekend.
The point of this post (at this time, anyhow) is to remind myself of the stupid issue I ran in to with the install/deploy of minishift on Fedora 31. Totally my fault, but not exactly intuitive what I happened to have done incorrectly. Let's roll...
I had ran through the standard install docs (which were fairly generic) and the following would occur:
$ minishft start
...
...
...
-- Minishift VM will be configured with ...
Memory: 8 GB
vCPUs : 2
Disk size: 40 GB
-- Starting Minishift VM .... FAIL E0118 20:17:12.659441 145997 start.go:494] Error starting the VM: Error creating new host: dial tcp: missing address. Retrying.
Error starting the VM: Error creating new host: dial tcp: missing address
I had ran through the standard install docs (which were fairly generic) and the following would occur:
$ minishft start
...
...
...
-- Minishift VM will be configured with ...
Memory: 8 GB
vCPUs : 2
Disk size: 40 GB
-- Starting Minishift VM .... FAIL E0118 20:17:12.659441 145997 start.go:494] Error starting the VM: Error creating new host: dial tcp: missing address. Retrying.
Error starting the VM: Error creating new host: dial tcp: missing address
I had install the driver using
I then found an independent blog detailing methods for many different variants and I found the one for fedora/centos (thanks ComputingForGeeks - link below)
$ sudo curl -L https://github.com/docker/machine/releases/download/v0.16.2/docker-machine-Linux-x86_64 -o /usr/local/bin/docker-machine-driver-kvm
$ chmod +x /usr/local/bin/docker-machine-driver-kvm
I then found an independent blog detailing methods for many different variants and I found the one for fedora/centos (thanks ComputingForGeeks - link below)
Comments
Post a Comment