[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: very newbie minishift question



Thanks. After recreating everything from scratch accessing the internal registry really worked.

Matthias

Am 13.02.19 um 06:59 schrieb Petr Kotas:
Hi Matthias,

when i played with minishift sometimes this happened. I just did reset and it worked. It might help to delete the local cluster by minishift delete and pull it again.

Petr

On Tue, Feb 12, 2019 at 5:05 PM Matthias Leopold <matthias leopold meduniwien ac at <mailto:matthias leopold meduniwien ac at>> wrote:

    Hi,

    I'm trying to get a littlebit into openshift by using minishift.
    I admit I didn't do a lot of basic research, bit I'm not getting
    anywhere...

    I got minishift running locally in KVM. I can login to the webinterface
    at https://192.168.42.78:8443/. Any deployments of the applications in
    the Catalog fail because "172.30.1.1:5000 <http://172.30.1.1:5000>"
    doesn't seem to be up. I then
    discovered the registry-route addon and applied it. I executed "docker
    login -u developer -p `oc whoami -t`
    docker-registry-default.192.168.42.78.nip.io
    <http://docker-registry-default.192.168.42.78.nip.io>" as advised,
    that fails
    with "Error response from daemon: Get
    https://docker-registry-default.192.168.42.78.nip.io/v1/users/: dial
    tcp
    192.168.42.78:443 <http://192.168.42.78:443>: getsockopt: connection
    refused". In the webinterface
    deployments still try to pull images from "172.30.1.1:5000
    <http://172.30.1.1:5000>"....

    How is this _supposed_ to work?

    thx
    matthias

    _______________________________________________
    users mailing list
    users lists openshift redhat com
    <mailto:users lists openshift redhat com>
    http://lists.openshift.redhat.com/openshiftmm/listinfo/users




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]