BTW If I would like to expose my registry to the outside world, would
executing the following command just do the job? I'm trying to expose the
registry via...

oc expose svc/docker-registry --hostname=192.168.1.21

...but connecting to http://192.168.1.21:5000 gives me Connection Refused.
I missed some steps here? :)

śr., 12 lip 2017 o 15:57 użytkownik Henryk Konsek <hekon...@gmail.com>
napisał:

> Many thanks. Integrated registry is exactly what I need and works like a
> charm :) .
>
> czw., 29 cze 2017 o 11:59 użytkownik Maciej Szulik <maszu...@redhat.com>
> napisał:
>
>> On Wed, Jun 28, 2017 at 11:53 AM, Frederic Giloux <fgil...@redhat.com>
>> wrote:
>>
>>> Hi Henryk
>>>
>>> If I correctly understand your use case I think that the easiest way is
>>> to create an imagestream foo and to use the pull-through feature:
>>>
>>> https://docs.openshift.org/latest/install_config/registry/extended_registry_configuration.html#middleware-repository-pullthrough
>>>
>>> https://docs.openshift.org/latest/dev_guide/managing_images.html#image-pull-policy
>>>
>>> Regards,
>>>
>>> Frédéric
>>>
>>> On Wed, Jun 28, 2017 at 11:29 AM, Henryk Konsek <hekon...@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> What would be the easiest way to start Docker Registry in OpenShift
>>>> Origin and tell OpenShift to look up for Docker images in it?
>>>>
>>>> What I would like to achieve is that when I execute "oc new-app foo",
>>>> OpenShift will try to look up for "foo" image in my local Origin registry
>>>> and then in DockerHub.
>>>>
>>>
>>
>> Just install the integrated registry and all you're asking for will be
>> there:
>> https://docs.openshift.org/latest/install_config/registry/index.html
>>
>>
>>
>> --
> Henryk Konsek
> https://linkedin.com/in/hekonsek
>
-- 
Henryk Konsek
https://linkedin.com/in/hekonsek
_______________________________________________
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to