Thanks.  That is the default name in many ansible scripts, then looking at
the ansible logs, it seems that it should be "
docker-registry-default.ocp-2.192.168.56.12.nip.io" ?
Even if the name is not the right one, I have no idea what to do to
investigate ???
I have uploaded the full ansible log here:
https://github.com/BrunoVernay/VM-images-packer/issues/2 I will try to read
it again to find some hints
Bruno



On Fri, Sep 1, 2017 at 11:23 AM Yu Wei <[email protected]> wrote:

> It seemed svc name was not correct.
>
> docker-registry.default.svc.cluster.local:5000
>
>
> Thanks,
>
> Jared, (韦煜)
> Software developer
> Interested in open source software, big data, Linux
> ------------------------------
> *From:* [email protected] <
> [email protected]> on behalf of Bruno Vernay <
> [email protected]>
> *Sent:* Friday, September 1, 2017 3:09:08 PM
> *To:* [email protected]
> *Subject:* Pushing image docker-registry.default.svc:5000/... failed
>
> Hi
> I have a clean install, systemctl show no apparent errors, but when trying
> to build my first app it fails:
> ------
> Writing lock file
> Generating optimized autoload files
> Pushing image
> docker-registry.default.svc:5000/picture-uploader/cam-cli:latest ...
> Warning: Push failed, retrying in 5s ...
> ...
>
> Registry server Address:
> Registry server User Name: serviceaccount
> Registry server Email: [email protected]
> Registry server Password: <<non-empty>>
> error: build error: Failed to push image: After retrying 6 times, Push
> image still failed
> -----
>
> And I may have done something really wrong because
>   oc logs dc/docker-registry
>   Error from server: deploymentconfigs.apps.openshift.io
> "docker-registry" not found
>
> I don't know where to look, any hint would be appreciated.  I just have a
> master and a node, I can recreate easily
> https://github.com/BrunoVernay/VM-images-packer
>
> Thanks
> Bruno
>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to