Looking directly at one of the nodes, I see it as this:
docker-registry.default.svc:5000/image-uploader/app-cli <none>
7234ee8e0215 2 days ago 647 MB
However, trying to pull it, I get:
# docker pull docker-registry.default.svc:5000/image-uploader/app-cli
Using default tag: latest
Trying to pull repository
docker-registry.default.svc:5000/image-uploader/app-cli ...
Pulling repository docker-registry.default.svc:5000/image-uploader/app-cli
Error: image image-uploader/app-cli:latest not found
On Wed, Jun 20, 2018 at 4:21 PM, Clayton Coleman <[email protected]>
wrote:
>
>
> On Jun 20, 2018, at 7:32 AM, Hetz Ben Hamo <[email protected]> wrote:
>
> With all redundant hardware these days, with UPS - power loss can happen.
>
> I just got a power loss and upon powering on those machines, most of the
> services weren't working. Checking the pods shows almost all of them in
> error state. I deleted the pods and they were automatically recreated so
> most of the services were running, but the images inside this Openshift
> system wen't dead (redeployed my stuff gave an error that images cannot be
> pulled).
>
>
> If you get “images cannot be pulled” it usually means those images don’t
> exist anymore. If you try to docker pull those images, what happens?
>
>
> I looked at the documents, both the commercial and the origin version, but
> there is nothing which talks about this issue, nor any script that will fix
> this issue after powering on this system.
>
> Is there such a document or any script that fixes such an issue?
>
> Thanks,
> Hetz
>
> _______________________________________________
> dev mailing list
> [email protected]
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
>
_______________________________________________
dev mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
