You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "James Netherton (JIRA)" <ji...@apache.org> on 2019/05/15 08:26:00 UTC

[jira] [Resolved] (CAMEL-13526) Docker component socket mode does not work

     [ https://issues.apache.org/jira/browse/CAMEL-13526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Netherton resolved CAMEL-13526.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0-M3
                   3.0.0

> Docker component socket mode does not work
> ------------------------------------------
>
>                 Key: CAMEL-13526
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13526
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-docker
>    Affects Versions: 3.0.0
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Minor
>             Fix For: 3.0.0, 3.0.0-M3
>
>
> When I recently upgraded the docker java client, I missed a change in behaviour for how the path to the docker daemon unix socket is determined. It used to be hard coded, but it's now configurable via the host URL:
> [https://github.com/docker-java/docker-java/commit/32220487c9f6fc54dceb152e774d3d09f5548943#diff-1e9098e0bf3cde696fe27648bc113a13]
> The camel-docker component cannot currently handle unix:// URL schemes in the host parameter because it erroneously appends the port number onto the end of the URL.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)