ed in open source software, big data, Linux
From: Łukasz Strzelec
Sent: Thursday, October 19, 2017 6:37:46 PM
To: Yu Wei
Cc: users@lists.openshift.redhat.com
Subject: Re: authentication required even for pulling images from private
registry
Hello:)
I had the same
Hello:)
I had the same issue. In our ENV we are obligated to use proxy server. Thus
we put to inventory statements regarding proxy. We forgot to add registry
to "noproxy" line. The result was exactly as you pointed.
I hope this may help you or at least guide to diffrent solution.
Best regards
Hi Jared,
can you post your Deployment config?
2017-10-19 2:37 GMT+02:00 Yu Wei :
> Image and pods are in the same project.
>
> Jared
> Interested in cloud computing,big data processing,linux
>
> 2017年10月19日 上午4:39于 Joel Pearson 写道：
> Is the image in a different project that which you’re trying t
Image and pods are in the same project.
Jared
Interested in cloud computing,big data processing,linux
2017年10月19日 上午4:39于 Joel Pearson 写道：
Is the image in a different project that which you’re trying to run it in?
Ie the image lives in project a and you’re trying to run the pod in project b
In
Is the image in a different project that which you’re trying to run it in?
Ie the image lives in project a and you’re trying to run the pod in project
b
In that scenario you need to grant some sort of permissions (image-pull or
something).
On Thu, 19 Oct 2017 at 4:32 am, Yu Wei wrote:
> Hi,
>
>
Hi,
I setup openshift origin cluster 3.6 and found a problem with private registry.
Image was failed to be pulled by work node with error as below,
rpc error: code = 2 desc = unauthorized: authentication required
However, the registry works well and I also could find the image via
docker-cons
