-
Bug
-
Resolution: Done
-
Minor
-
4.5.0.AM2
-
devex #138 September 2017
- ASSERT: make sure that you have a minishift that does NOT have a docker registry.
[adietish@localhost minishift]$ ./minishift openshift registry No information found for 'service/docker-registry'
You can achieve that by :
- have server adapter stopped, minishift started
- logging into your cdk with oc as "admin" and then:
oc project default oc delete svc docker-registry
Once the service is deleted you need to start the cdk.
- ASSERT: make sure that you have a connection to the CDK/minishift in Eclipse
- ASSERT: make sure that you have a server adapter for your CDK/minishift in Eclipse
- EXEC/ASSERT: make sure that your CDK/minishift server adapter is started
- EXEC: edit the OpenShift connection
- ASSERT: connection wizard shows up
- EXEC: hit "Advanced" so that the "Image Registry URL" text field shows up
- EXEC: hit "Discover"
Result
An error dialog shows up telling you no registry provider could be found
the behaviour is shown in the following screencast: https://www.youtube.com/watch?v=DMdby-Oc54M&feature=youtu.be
- is related to
-
JBIDE-25014 only insert the registry url if there's no value yet / ask for confirmation
- Closed
-
JBIDE-25046 Can't find CDK for registry discovery when 2 connections are defined for CDK
- Closed
- relates to
-
JBIDE-24491 CDK Server adapter: allow users to look up the address of the docker registry
- Closed
-
JBIDE-25093 IT: create tests for the Docker discovery feature
- Closed