[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-23136:
-------------------------------------
Sprint: devex #123 November 2016 (was: devex #123 November 2016, devex #130 April 2017)
> 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.4.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)
9 years
[JBoss JIRA] (JBIDE-24228) WildFly 11 will fails to stop unless credentials are set up
by Martin Malina (JIRA)
Martin Malina created JBIDE-24228:
-------------------------------------
Summary: WildFly 11 will fails to stop unless credentials are set up
Key: JBIDE-24228
URL: https://issues.jboss.org/browse/JBIDE-24228
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.4.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
The new WildFly 11 adapter is able to start the server, but when you stop it, you get an error:
Server WildFly 11 failed to stop.
Rob suggested to set up credentials and then it will work. That's true, but it still doesn't explain why this doesn't work without credentials locally as it should and as is the case with all the other server types.
To make sure this works outside of Eclipse, I started WildFly 11 from console, then in another window I ran jboss-cli.sh, connected (no password) and then was able to shutdown the server successfully.
So this needs to some investigation as to why this fails from Eclipse.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years