[
https://issues.apache.org/jira/browse/JCLOUDS-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301911#comment-15301911
]
ASF subversion and git services commented on JCLOUDS-1117:
----------------------------------------------------------
Commit c269e01610d634d340d1e9a1c8d24dc6f2311805 in jclouds-labs's branch
refs/heads/master from [~kwart]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=c269e01 ]
[JCLOUDS-1117] fix for advanced Docker configuration - the Config.Builder
should stay unchanged if used
> Some values from DockerTemplateOptions.configBuilder are replaced in
> DockerComputeServiceAdapter
> ------------------------------------------------------------------------------------------------
>
> Key: JCLOUDS-1117
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1117
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-labs
> Reporter: Josef Cacek
> Labels: docker
>
> *Issue description:*
> If I want to use advanced Docker configuration by providing
> {{DockerTemplateOptions.configBuilder(...)}}, then some values are replaced
> (exposed ports, port bindings) by configuration from the
> {{DockerTemplateOptions}} configuration. This is wrong, because by providing
> the {{Config.Builder}} instance I say I want to use exactly this
> configuration.
> *Expected state:*
> If the {{Config.Builder}} instance is provided, then it's used directly
> (unchanged).
> *Suggested fix:*
> The condition block {{if (containerConfigBuilder == null) \{}} should be
> extended.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)