[JBoss JIRA] (ERT-325) Improvements on the 'push image' dialog [EBZ#496922]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-325:
---------------------------------------
Summary: Improvements on the 'push image' dialog [EBZ#496922]
Key: ERT-325
URL: https://issues.jboss.org/browse/ERT-325
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.1 (4.6)
- The tag should be verified before attempting to apply it (see problem reported by OpenShift tooling on JBoss Tools: https://issues.jboss.org/browse/JBIDE-22580)
- The '-force' flag should be available to force tagging the selected image
- The image should optionally remained tagged upon push operation completion, if the user wants to see it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22580) Deploy Docker Image wizard: Cannot push already tagged image to docker registry
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-22580:
---------------------------------------
Suggestion reported upstream in https://bugs.eclipse.org/bugs/show_bug.cgi?id=496922, amongst other proposals.
> Deploy Docker Image wizard: Cannot push already tagged image to docker registry
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22580
> URL: https://issues.jboss.org/browse/JBIDE-22580
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, docker, openshift_v3
> Fix For: 4.4.1.M1
>
>
> There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace
> {code}Failed to push the selected Docker image into OpenShift registry
> org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083)
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-238) Issue in DockerConnection#hasImage(String, String) [EBZ#495243]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-238?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-238:
------------------------------
Issue Type: Bug (was: Task)
Fix Version/s: Neon.1 (4.6)
Affects Version/s: Neon (4.6)
> Issue in DockerConnection#hasImage(String,String) [EBZ#495243]
> --------------------------------------------------------------
>
> Key: ERT-238
> URL: https://issues.jboss.org/browse/ERT-238
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Roland Grunberg
> Labels: Docker, bzira
> Fix For: Neon.1 (4.6)
>
>
> The method only inspects the first 'repo' value for a given image, so if a given Docker image was tagged with different names (eg: 'jboss/wildfly' and 'xcoulon/wildfly'), then one method call will respond 'false' while it should be 'true'.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-250) Cannot deploy image from local repository to remote registry [EBZ#495793]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-250?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-250:
------------------------------
Issue Type: Bug (was: Task)
> Cannot deploy image from local repository to remote registry [EBZ#495793]
> -------------------------------------------------------------------------
>
> Key: ERT-250
> URL: https://issues.jboss.org/browse/ERT-250
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Roland Grunberg
> Priority: Critical
> Labels: Docker, bzira
>
> I have a docker connection to local host and a remote registry account in Registry Accounts preference page. For better understanding there is my setup:
> - docker host running on local machine (socket at /var/run/docker.sock)
> - registry at hub.openshift.rhel-cdk.10.1.2.2.xip.io
> - copied registry certificate to local machine to folder /etc/docker/certs.d/hub.openshift.rhel-cdk.10.1.2.2.xip.io/ca.crt (this is necessary because it is docker registry with self-signed certificate and not running with --insecure-registry)
> - any local docker image (build locally, not presented on docker hub)
> When I am working from command line I do following:
> - log in to docker registry hub.openshift.rhel-cdk.10.1.2.2.xip.io with credentials (certificate of docker registry must be present on local machine)
> - tag a docker image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha
> - push the tagged image to registry
> When I am working from IDE with docker tools, I select context menu item Push in the context menu of a docker image and select the registry. At first it is trying to push layers to registry but in the end I get following error without any stack trace
> "com.spotify.docker.client.DockerException:
> org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha:latest: unknown: request access to the resource is denied".
> With docker client from command line everything works ok.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months