You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2020/01/07 07:35:00 UTC

[jira] [Commented] (JAMES-3021) When using a docker network, the container ip is not resolved the right way

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

Benoit Tellier commented on JAMES-3021:
---------------------------------------

https://github.com/linagora/james-project/pull/3033 contributed a fix

> When using a docker network, the container ip is not resolved the right way
> ---------------------------------------------------------------------------
>
>                 Key: JAMES-3021
>                 URL: https://issues.apache.org/jira/browse/JAMES-3021
>             Project: James Server
>          Issue Type: Bug
>          Components: tests
>            Reporter: Matthieu Baechler
>            Priority: Major
>
> There are various setup of docker use and it's quite hard to know what IP should be used in those various situations.
> Until now, we found a solution that solved local dev on linux and mac and CI at the same time.
> Now we want to use docker networks to run several containers in a network during tests and container IP is not resolved to the container IP in this network (that should be reachable because docker takes care of the routing table).
> Let's try to fix all these cases at once (and maybe upstream the solution to testcontainers project once done)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org