[
https://issues.apache.org/jira/browse/DIRSERVER-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933480#comment-15933480
]
Stefan Seelmann commented on DIRSERVER-2182:
--------------------------------------------
I think I already explained partially here:
https://mail-archives.apache.org/mod_mbox/directory-users/201703.mbox/%3Cee5ef27d-3ae4-e573-ab0c-2bceb443d012%40stefan-seelmann.de%3E
Within the Docker container, assuming you use default "bridge" networking, the
localhost/127.0.0.1 (loopback) address is only visible within the container. So
it's plain normal that you have to configure a service to listen either to all
(0.0.0.0) or the eth0 (in Docker bridged network by default 172.17.x.y) network
interfaces because only the 172.17/16 network can be mapped to the outer world.
Of course you can start the container with "--network host" then the host
network is used within the container.
> Apaches 2.0.0-M23 embedded instance cannot run correctly within docker
> container
> --------------------------------------------------------------------------------
>
> Key: DIRSERVER-2182
> URL: https://issues.apache.org/jira/browse/DIRSERVER-2182
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M23
> Environment: ApacheDS Embedded instance, dropwizard and Docker 2.x
> Reporter: harish sat
> Fix For: 2.0.0-M23
>
>
> While running current instance within docker container, the ldapserver does
> not bind on a specified port, no error message or exception thrown. It works
> fine as a standalone instance but there is a problem within docker container
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
