Hi, Sangeetha,

Sorry to hear you're running into difficulties. First, can you verify that
you're intending to run the public Docker Hub image at
https://hub.docker.com/r/jboss/drools-workbench-showcase on the Cloud
Foundry instance you're targeting? If that's the case, the issue isn't that
the Docker staging task can't connect to an insecure registry, it's that it
can't connect to Docker Hub on the public Internet.

Are you in control of your CF+Diego deployment? If so, can you provide some
details about it? As a start, it would help to know which versions of the
CF and Diego releases you have deployed, what infrastructure they are
deployed to, and how you're generating your deployment manifests (for
example, via the manifest-generation scripts in cf-release and
diego-release, or manually). Also, can you push other apps successfully?
For example, can you push a buildpack app that makes an HTTP or HTTPS
connection to some other service on the public Internet and verify that
that app stages, runs, and connects to that service correctly?

Thanks,
Eric, CF Runtime Diego PM

On Thu, Apr 21, 2016 at 6:20 PM, Tomoe Sugihara <tsugihara(a)pivotal.io>
wrote:

On Fri, Apr 22, 2016 at 3:31 AM, James Myers <jmyers(a)pivotal.io> wrote:

Hi,

You can set this property
(

https://github.com/cloudfoundry-incubator/diego-release/blob/develop/jobs/stager/spec#L78-L80
)

on your Diego deployment to add insecure docker registries that are

publicly

available.

Looks like that file is gone by the commit:

https://github.com/cloudfoundry-incubator/diego-release/commit/a8468ab7ded8d7408aa3274395671e10a3ab5334#diff-4efdf9a6a5de284f5f98a81bef3a2788L78

I found the setting here instead:

https://github.com/cloudfoundry/capi-release/blob/ee42bd82a51875d462299b9ada92cf08a5c52f8f/jobs/stager/spec#L81

And I think it is related to this change:

https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/PVD6TC6TQVOEICYY2H6ZFZ4CUMMZIPEU/

Thanks,
Tomoe