On Sun, Dec 16, 2018 at 5:36 AM Gerard Braad <me(a)gbraad.nl> wrote:
`minishift ip` is only slow when used with `minishift ip
and this is because it writes into the VM
in this case, it is only "minishift ip"
but also minishift start is negatively impacted such as 25+ minutes on a
"minishift start" on some networks (after everything has been cached)
The general command should not be, as it would only return the VM
information (directly from the hypervisor)
Also, what is the hypervisor/OS combination in question here?
MacOS + Virtualbox
and it is only slow on "some Wifi networks"
Perhaps you should be running a bridged setup, so you aren't affected
so much by the changing IP.
If on macOS, you're kinda out of luck here... although perhaps you can
bind on a tun/tap setup?
These are things that I never touch, just defaults for VirtualBox +
With my networking hoping, I am getting:
- new IP assigned DHCP
- new DNS
what else that might be impacting the behavior of virtualbox?
On Sat, Dec 15, 2018 at 11:36 PM Burr Sutter <bsutter(a)redhat.com> wrote:
> I might change networks more often than underwear.
> And those networks are often in various indecently countries, often in
hotels and conference centers/meeting rooms.
> And one thing that I have seen lately is that commands like "minishift
ip" become really, really slow.
> This is problematic because I use "minishift ip" in my scripts for
curling my NodePort-based (or Route-based) Service.
> What theories do you all have as it relates to that command?
> Minishift Mailing List mailing list -- minishift(a)lists.minishift.io
> To unsubscribe send an email to minishift-leave(a)lists.minishift.io
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]