[jbosstools-issues] [JBoss JIRA] (JBIDE-22686) Can't push image to docker registry

[Dmitry Bocharov (JIRA)]

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

Dmitry Bocharov commented on JBIDE-22686:
-----------------------------------------

[~hardy.ferentschik],
{code:shell}
[vagrant at rhel-cdk ~]$ ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 52:54:00:ab:b6:9e brd ff:ff:ff:ff:ff:ff
    inet 192.168.121.51/24 brd 192.168.121.255 scope global dynamic eth0
       valid_lft 2384sec preferred_lft 2384sec
    inet6 fe80::5054:ff:feab:b69e/64 scope link 
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 52:54:00:09:6a:57 brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 
    link/ether 02:42:5b:82:ad:f4 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:5bff:fe82:adf4/64 scope link 
       valid_lft forever preferred_lft forever
10: veth046d304 at if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP 
    link/ether 2a:b6:bf:85:4a:d4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::28b6:bfff:fe85:4ad4/64 scope link 
       valid_lft forever preferred_lft forever
{code}

{code:shell}
[vagrant at rhel-cdk ~]$ ping 10.1.2.2
PING 10.1.2.2 (10.1.2.2) 56(84) bytes of data.
>From 192.168.121.1 icmp_seq=1 Destination Port Unreachable
>From 192.168.121.1 icmp_seq=2 Destination Port Unreachable
{code}

yes, i tried vagrant destroy and vagrant up several times.
I also tried every step from home (where i have router - thought it could be the reason of the problem) and from the office.

So now i think the problem is because 10.1.2.2 is unreachable. Am i right?



> Can't push image to docker registry
> -----------------------------------
>
>                 Key: JBIDE-22686
>                 URL: https://issues.jboss.org/browse/JBIDE-22686
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: docker, openshift
>    Affects Versions: 4.4.0.Final
>         Environment: Fedora 23
>            Reporter: Dmitry Bocharov
>            Assignee: Dmitry Bocharov
>             Fix For: 4.4.x
>
>         Attachments: DeployDockerImageToOS.webm
>
>
> The screencast of the last steps is attached. 
> Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way.
> Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings.
> _exception:_
> org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
>  v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> 	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047)
> 	at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67)
> 	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)
> Caused by: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
>  v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> 	at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42)
> 	at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74)
> 	at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821)
> 	at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043)
> 	... 3 more
> Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/
> v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused
>  v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused
> 	at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49)
> 	at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40)
> 	... 6 more



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)