I seem my confusion - our tutorial says "use minishift" and you broke the
rules with "oc cluster up" :-)

For now, I prefer to stick with minishift as "oc cluster up" is for
upstream contributors while minishift more for end-users.

I suspect the Openshift team would not want "oc docker-env".   You can only
expose the docker daemon when it runs on localhost and "oc" is used for any
openshift cluster.  In general, it is simply harder to work with a remote
openshift + docker images.

On Sat, Apr 14, 2018 at 9:51 PM, Gary Lamperillo <glamp...@redhat.com>

> Hi All,
>   This is not a bug, just a different way to get the docker-env based on
> the way you install openshift.  I mentioned this to Burr/Rafael, so they
> could document it for the tutorial and give another install option to work
> with.  But, here is a question, wouldn’t it be better if when you ‘oc
> login’ to any environment, you could get the docker-env?   So, what I
> propose is a ‘oc docker-env’ or ‘oc env’ to set your local docker build
> settings or other important settings that may be needed in the future.
> Does this make sense?
> Thanks,
> Gary
> On Sat, Apr 14, 2018 at 7:13 AM Burr Sutter <bsut...@redhat.com> wrote:
>> Gary has been running through bit.ly/istio-tutorial but using Openshift
>> 3.9 (not sure which minishift version) and believes that "minishift
>> docker-env" is not setting things up correctly.
>> here is his comment
>> "So, I confirmed it works with OCP 3.9, just one thing really needs to
>> change from minishift install, use - "docker-machine env openshift",
>> instead of the command eval$(minishift docker-env)"
>> --
> Gary Lamperillo
> Principal Applications Architect, Channels Application Platform Partner
> Program
> glamp...@redhat.com
> linkedin.com/in/glamperi-redhat
> <http://www.linkedin.com/in/glamperi-redhat>
> (M) 310-896-5282
Devtools mailing list

Reply via email to