On Tue, Jul 24, 2018 at 9:05 AM Gerard Braad <[email protected]> wrote:

> Yes
>

Do I need to re-run that command after every "start" or just the initial
start (creation of the VM)?


> On Tue, Jul 24, 2018 at 10:01 PM Burr Sutter <[email protected]> wrote:
> >
> >
> >
> > On Tue, Jul 24, 2018 at 8:53 AM Gerard Braad <[email protected]> wrote:
> >>
> >> At what point in the instructions do you actually use the `m ip
> >> --set-static` option?
> >
> >
> > Normally I use the command like so
> > minishift profile set istio-tutorial
> > minishift config set memory 8GB
> > minishift config set cpus 3
> > minishift config set vm-driver virtualbox
> > minishift config set image-caching true
> > minishift addon enable admin-user
> > minishift addon enable anyuid
> > minishift ip --set-static
> >
> > minishift start
> >
> > and I think you are telling me to move the --set-static below the start
> command
> >
> >> I do not see them in the instructions / steps to reproduce.
> >>
> >> As in the previous email mentioned. Be sure to do:
> >>
> >> ```
> >> m start
> >> m ip --set-static
> >> m start --profile newthing
> >> m ip --set-static
> >> m profile set lastestthing
> >> m start
> >> m ip --set-static
> >> ```
> >>
> >> This means you can ONLY make the IP sticky after it has been
> >> provisioned to the VM on start once.
> >> Note: Only for Hyper-V you can provide it on startup.
> >>
> >> On Tue, Jul 24, 2018 at 9:47 PM Budh Ram Gurung <[email protected]>
> wrote:
> >> >
> >> > Here is the upstream ticket
> https://github.com/minishift/minishift/issues/2629.
> >> >
> >> > Regards,
> >> > Budh Ram Gurung
> >> >
> >> >
> >> > On Tue, Jul 24, 2018 at 7:02 PM Budh Ram Gurung <[email protected]>
> wrote:
> >> >>
> >> >> Hi Burr,
> >> >>
> >> >> On Tue, Jul 24, 2018 at 6:50 PM Burr Sutter <[email protected]>
> wrote:
> >> >>>
> >> >>> Here is the seriousness of the situation.  I use profiles - like so
> >> >>> minishift profile set demo1
> >> >>> minishift start
> >> >>> # do some demo
> >> >>> minishift stop
> >> >>> minishift profile set demo2
> >> >>> minishift start
> >> >>> # do some other demo
> >> >>> minishift stop
> >> >>> minishift profile set demo3
> >> >>> minishift start
> >> >>> # yet other demo
> >> >>> minishift stop
> >> >>> # close laptop, drive/fly to next location, repeat the whole process
> >> >>>
> >> >>> Yet, at the next location, I get a new IP address and the following
> error.  This particular VM's IP was 106, yet it reverted back to 101.
> >> >>>
> >> >>> Caused By:
> >> >>> Error: Get https://192.168.99.101:8443/healthz/ready: x509:
> certificate is valid for 10.0.2.15, 127.0.0.1, 172.17.0.1, 172.30.0.1,
> 192.168.99.106, not 192.168.99.101
> >> >>
> >> >>
> >> >> Thanks for taking time and reporting the issue.
> >> >> We will definitely look into it and creating an upstream issue to
> track it.
> >> >>
> >> >>>
> >> >>> the demos are basically:
> >> >>> bit.ly/msa-instructions
> >> >>> bit.ly/istio-tutorial
> >> >>> bit.ly/faas-tutorial
> >> >>> and you can not really run 2 of these in the same VM due to the 10
> pods per core limit.
> >> >>>
> >> >>> minishift ip --set-static does not seem to make the IP "sticky".
> >> >>> It really wants to go back to 100.  It seems the IP address is not
> "stored" in the profile.
> >> >>> So, this makes profiles essentially unusable.
> >> >>>
> >> >>> creation script:
> >> >>> minishift profile set istio-tutorial
> >> >>> minishift config set memory 8GB
> >> >>> minishift config set cpus 3
> >> >>> minishift config set vm-driver virtualbox
> >> >>> minishift config set image-caching true
> >> >>> minishift addon enable admin-user
> >> >>> minishift addon enable anyuid
> >> >>> # minishift ip --set-static
> >> >>>
> >> >>> minishift start
> >> >>> _______________________________________________
> >> >>> Devtools mailing list
> >> >>> [email protected]
> >> >>> https://www.redhat.com/mailman/listinfo/devtools
> >> >>
> >> >>
> >> >> Regards,
> >> >> Budh Ram Gurung
> >> >
> >> > _______________________________________________
> >> > Devtools mailing list
> >> > [email protected]
> >> > https://www.redhat.com/mailman/listinfo/devtools
>
_______________________________________________
Devtools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/devtools

Reply via email to