You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/24 22:22:41 UTC

[jira] [Commented] (CAMEL-11069) Make docker socket support usable

    [ https://issues.apache.org/jira/browse/CAMEL-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941246#comment-15941246 ] 

ASF GitHub Bot commented on CAMEL-11069:
----------------------------------------

GitHub user jhliptak opened a pull request:

    https://github.com/apache/camel/pull/1570

    CAMEL-11069 docker socket support

    pull request for https://issues.apache.org/jira/browse/CAMEL-11069 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jhliptak/camel CAMEL-11069

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1570.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1570
    
----
commit 142b6e59c0c8bba1926d28558a6feb1e20c711e8
Author: John Liptak <jo...@centurylink.com>
Date:   2017-03-24T22:20:45Z

    CAMEL-11069 docker socket support

----


> Make docker socket support usable
> ---------------------------------
>
>                 Key: CAMEL-11069
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11069
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-docker
>    Affects Versions: 2.18.3
>         Environment: Linux docker enviroments
>            Reporter: John Liptak
>            Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Our docker environment does not expose the remote API socket over TCP, so I wanted to get the unix:///var/run/docker.sock endpoint to work.
> This needed two changes:
> 1. The DockerClientProfile toUrl() method appends a :port which is not valid for the unit port.
> 2. The URI parameter for socket has the wrong name and isn't in the valid URI parameters map.
> I will submit a pull request once I have the issue #.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)