[jbosstools-issues] [JBoss JIRA] (JBIDE-22915) Deploy Docker Image: Replication controller is not created for some images

[Jeff Cantrill (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290548#comment-13290548 ] 

Jeff Cantrill commented on JBIDE-22915:
---------------------------------------

[~jeffmaury] You would need to expose it somehow as a route on the registry pod, but I don't know if that is the same.  The pod is a docker registry which utilizes the docker daemon where your local machine has a docker daemon and the docker ui 'knows' how to interface with it.  It was my understanding that if you use the cdk it would use the daemon on your underlying host.  I'll see if I can get some information on how 'oc cluster up' utilizes the host daemon... though I don't know if it was available for 1.2

> Deploy Docker Image: Replication controller is not created for some images
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-22915
>                 URL: https://issues.jboss.org/browse/JBIDE-22915
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.1.AM3
>            Reporter: Marián Labuda
>            Assignee: Jeff MAURY
>              Labels: deploy_docker_wizard, openshift_v3
>             Fix For: 4.4.2.AM1
>
>
> When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1")



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)