[jbosstools-issues] [JBoss JIRA] (ERT-250) Cannot deploy image from local repository to remote registry [EBZ#495793]
Friendly Jira Robot (JIRA)
issues at jboss.org
Thu Jun 9 10:26:00 EDT 2016
Friendly Jira Robot created ERT-250:
---------------------------------------
Summary: 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: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
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)
More information about the jbosstools-issues
mailing list