[jbosstools-issues] [JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

[Dmitrii Bocharov (JIRA)]

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

Dmitrii Bocharov commented on JBIDE-23136:
------------------------------------------

According to https://docs.openshift.com/container-platform/3.3/dev_guide/managing_images.html#creating-an-image-stream-by-manually-pushing-an-image: an Image Stream is created by manually pushing an image to the internal registry. 
I debugged the workflow from the description of this JIRA. Right after pushing image to registry phase and before deploying image job, i found that the only resource created in Openshift is an Image Stream:
 !FedoraImageStream.png|thumbnail! 
And you can see there the address of the fedora image in internal registry: 
{quote}dockerImageRepository: '172.30.115.181:5000/sample-project/fedora'{quote}
By this moment "docker images -a" still doesn't have this additional image.

Then starts [Deploy Image job and creation of resources|https://github.com/jbosstools/jbosstools-openshift/blob/57ef9c017e8a2d12cb918ecac2af62c1bb86d308/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/job/DeployImageJob.java#L159]. And right after creation of Deployment Config, "docker images -a" starts displaying this additional image.

About the tag: it doesn't have tag, but it displays the digest:  !ImagesWithDigest.png|thumbnail! 

So in my opinion this is an intended behavior, though i'm no really acquainted with this stuff. So [~jcantrill] [~xcoulon] [~adietish], please comment, what do you think about it


> Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-23136
>                 URL: https://issues.jboss.org/browse/JBIDE-23136
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.1.Final
>            Reporter: Marián Labuda
>            Assignee: Dmitrii Bocharov
>              Labels: deploy_docker_wizard, openshift_v3
>             Fix For: 4.4.3.AM2
>
>         Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png
>
>
> I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see:
> 172.30.192.49:5000/msa/msa         <none>      238200ae067d        4 months ago        1.05 GB
> Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411
> Steps to reproduce:
> - have a project with a file named {{Dockerfile}} with the following content (1 line):
> {code}
> FROM fedora:latest
> {code}
> - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}})
> - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. 
> - In the wizard, select the option to push the image to the registry (add a dummy port if needed)
> - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI)



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)