[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23136:
---------------------------------------
If you have been able to pull image with no tag, that means that the image is probably already in the registry with no tag. Probably because the digest is better/more precise identifier.... Not sure.
> 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
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: 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
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23136:
-------------------------------
Attachment: local-docker-images-after-pull-1.png
> 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
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: 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
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-23136:
------------------------------------
I think it's related docker and pulling images by SHA256.
Here is the result on my local Docker of the command: docker pull registry.access.redhat.com/jboss-eap-6/eap64-openshift@sha256:35aac91f89e...
[^local-docker-images-after-pull-1.png]
> 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
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: 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
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Jeff MAURY edited comment on JBIDE-23136 at 9/8/16 7:31 AM:
------------------------------------------------------------
I'm not sure this is so related to Docker push.
See the images when creating a new app using eap64-basic-s2i from JBossTools [^eap64-basic-s2i-new-app-from-jbosstools-1.png]
See the images when creating a new app using eap64-basic-s2i from CLI [^eap64-basic-s2i-new-app-from-cli-1.png]
was (Author: jeffmaury):
I'm not sure this is so related to Docker push. See the images when creating a new app using eap64-basic-s2i from JBossTools [^eap64-basic-s2i-new-app-from-jbosstools-1.png]
> 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
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-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
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23136:
-------------------------------
Attachment: eap64-basic-s2i-new-app-from-cli-1.png
> 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
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-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
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23143) Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23143?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23143:
---------------------------------------
[~mickael_istria], thanks for the explanation and following up on this. Radim used the SDK package and didn't have this problem, because that package probably doesn't contain this wrong plugin/feature.
> Cannot install JBoss Tools 4.4.1.Final into Eclipse Neon.1 RC2
> --------------------------------------------------------------
>
> Key: JBIDE-23143
> URL: https://issues.jboss.org/browse/JBIDE-23143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.4.1.Final
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Attachments: neon-1-byoe.png, neon-1-remediation.png, update-sites-enabled.png
>
>
> When I try to install JBoss Tools 4.4.1.Final [1] Abridged category into eclipse-java-neon-1-RC2-macosx-cocoa-x86_64.tar.gz , I am shown a remediation screen.
> !neon-1-remediation.png!
> If I choose Update my installation, it offers to install what I want, but uninstall Eclipse XML Editors and Tools.
> This is the original error message (third option):
> {code}
> Your original request has been modified.
> "Code Recommenders Snipmatch" will be ignored because a newer version is already installed.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> Software currently installed: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> Only one of the following can be installed at once:
> Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.jar 3.8.0.v201605120129)
> Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.jar 3.9.0.v201608061824)
> Cannot satisfy dependency:
> From: Eclipse Web Developer Tools 3.8.0.v201606030549 (org.eclipse.wst.web_ui.feature.feature.group 3.8.0.v201606030549)
> To: org.eclipse.wst.xml_ui.feature.feature.group [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.8.0.v201605120129 (org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201605120129)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.8.0.v201605120129]
> Cannot satisfy dependency:
> From: Eclipse XML Editors and Tools 3.9.0.v201608061824 (org.eclipse.wst.xml_ui.feature.feature.group 3.9.0.v201608061824)
> To: org.eclipse.wst.xml_ui.feature.feature.jar [3.9.0.v201608061824]
> Cannot satisfy dependency:
> From: JBoss WebServices Tools 1.9.1.v20160608-0648 (org.jboss.tools.ws.feature.feature.group 1.9.1.v20160608-0648)
> To: org.eclipse.wst.web_ui.feature.feature.group [3.3.2,4.0.0)
> {code}
> [1] http://download.jboss.org/jbosstools/neon/staging/updates/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23136:
---------------------------------------
Pure docker pushing to registry works fine. I've tested it yesterday with Xavier.
> 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
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: eap64-basic-s2i-new-app-from-jbosstools-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
(v6.4.11#64026)
9 years, 7 months