minishift

How do I push to minishift's built-in docker registry?

巧了我就是萌 提交于 2021-02-08 10:04:08
问题 I'm trying to push a tagged build to minishift's built-in custom registry so I can use that image in OpenShift. I keep running into a permission issue. How do I get around this? $ docker push $registry/tutorial1/start The push refers to a repository [172.30.1.1:5000/tutorial1/start] e20ac34b31e3: Preparing 8890c47716ac: Preparing 787471275018: Preparing ee0ebee0324c: Preparing a30cfc27bb5d: Preparing d22688b29911: Waiting 08127eb3eb76: Waiting a637c551a0da: Waiting 2c8d31157b81: Waiting

Openshift: get access to openshift docker registry

大兔子大兔子 提交于 2019-12-13 05:11:18
问题 I've exposed my openshift registry: $ oc get routes -n default NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD docker-registry docker-registry-default.192.168.99.104.nip.io docker-registry 5000-tcp None Nevertheless, I'm trying to get access on that registry, but I've not been able to figure out what's wrong: docker login -p ngRslZJYJ40WxBA6YQbE5nMDK1Gh-cSWgnJCKR4EJ2I docker-registry-default.192.168.99.104.nip.io -u unused This command keeps stuck. 回答1: If the route is configured with

Minishift start using hyper-v on windows 10 fails with E1011

笑着哭i 提交于 2019-12-13 03:17:33
问题 Windows 10 Version 1607 minishift v1.3.1+a2d3799 CDK v3.1.1-1 Vagrant 2.0.0 When I try to start minishift I'm getting an error pretty early on: PS C:\minishift> minishift start Starting local OpenShift cluster using 'hyperv' hypervisor... E1011 16:57:09.569574 13196 start.go:282] Error starting the VM: Error starting stopped host: exit status 1. Retrying E1011 16:57:12.173524 13196 start.go:282] Error starting the VM: Error starting stopped host: exit status 1. Retrying E1011 16:57:14.765997

Could not access a running Docker Image of War (with tomcat) in minishift - OpenShift-Origin

匆匆过客 提交于 2019-12-12 02:08:09
问题 I have crated a docker image for a simple Java-Spring MVC War file, (Docker Config below). I am able to run the using docker run command and also I do not see any errors in the log or trouble uploading war into internal registry in Openshift-minishift. I was able to pull the image in my Openshift-minishift console. #Docker Config FROM tomcat:8.0.20-jre8 MAINTAINER ashok.gudise@github ENV CATALINA_HOME /usr/local/tomcat ENV PATH $CATALINA_HOME/bin:$PATH RUN mkdir -p "$CATALINA_HOME" WORKDIR

minishift start using HyperV fails when devtools installed on a different drive than /Users

落爺英雄遲暮 提交于 2019-12-11 14:39:55
问题 Is there a known issue wrt installing RH DevelopmentTools to D: when running minishift? I installed to D:\DevelopmentTools, which created a C:\Users\rcoe.minishift directory, in which the RHEL iso is located. Config looks correct: > D:\DevelopmentSuite>minishift config view > - iso-url : file://C:/Users/rcoe/.minishift/cache/iso/minishift-rhel7.iso > - memory : 4096 > - vm-driver : hyperv Yet, when I try to start minishift, it cannot locate the iso. From the error condition, it's not obvious

Minishift: Could not resolve: *.192.168.64.2.nip.io

强颜欢笑 提交于 2019-12-10 16:36:13
问题 I have installed minishift on OSX with brew: brew cask install minishift-beta ... $ minishift version Minishift version: 1.0.0 I have sucessfuly started minishift, and created node-ex example application and exported it: $ oc get route NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD nodejs-ex nodejs-ex-myproject.192.168.64.2.nip.io nodejs-ex 8080-tcp None However I can not reach .192.168.64.2.nip.io : $ curl nodejs-ex-myproject.192.168.64.2.nip.io curl: (6) Could not resolve host: