Thanks. How can I handle this when I'm using my own images?
maybe a more clear explanation:
We are using our own docker registry which is secured with a selfsigned certificate. So if we place the cert on our openshift node we're able to pull. We pulled the openshift-origin images v1.2.0 from dockerhub and pushed it inside our docker registry. We are using the registry instead of docker.io/openshift/origin-xxx
This works fine for our router, registry, cluster metrics project etc..
But when we are deploying the logging project: https://docs.openshift.org/latest/install_config/aggregate_logging.html it doesn't work.
the pull of the
But the problem raises later. The fluentd image is also pulled fine (from our registry).
But the images of the rest aren't pulled in the right way,
example of error events/logs: (origin-logging-"empty" is probably an issue?)
From: agoldste redhat com
Date: Thu, 7 Jul 2016 16:34:29 -0400
Subject: Re: Back-off pulling image "/origin-logging-curator sha256:b89cbdfc4e0e7d594f7a49c7581ae3f75b9d0313fce2ed8be83ee5c0426af72d"
To: dencowboy hotmail com
CC: users lists openshift redhat com
On Thu, Jul 7, 2016 at 3:48 PM, Den Cowboy <dencowboy hotmail com> wrote:
Did you push the image using Docker 1.10 and your node is running Docker 1.9?
If you're using ImageChangeTriggers, we translate tags to content-addressable IDs for consistent image usage so that a moving tag such as "latest" doesn't yield different images and possibly results when you deploy today, tomorrow, next week, etc.