According to the off line thread Minishift ip set status must be run after the vm is started
Le lun. 23 juil. 2018 à 05:04, Gerard Braad <[email protected]> a écrit : > It would be very unlikely the same IP address is used, as the address > is collected from the actual VM and stored inside. > But let's see what happened... Can you try to dump the contents of the > config file with: > > minishift ssh -- cat /var/lib/minishift/networking-* > > > On Mon, Jul 23, 2018 at 5:41 AM Burr Sutter <[email protected]> wrote: > > > > I might have an misunderstanding of "minishift ip --set-static" > > > > I am trying to have many profiles for the various demo arrangements that > I run. > > > > I thought I would always use "set-static" to address 509 cert error that > tends to pop-up between "start", "stop" and "start" [1] > > > > But, it seems that if you use "minishift ip --set-static" with more than > one profile, it attempts to reuse the same IP address with other profiles. > > > > I really do need too be able to switch profiles "on-the-fly" during > presentations > > minishift profile set istiodemo > > minishift start > > minishift stop > > minishift profile set openwhiskdemo > > minishift start > > minishift profile set microservices > > minishift start > > > > > > > > > > [1] Caused By: > > > > Error: Get https://192.168.99.102: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.104, not 192.168.99.102 > > _______________________________________________ > > Devtools mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/devtools > > _______________________________________________ > Devtools mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/devtools >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
