Hi Stefan Thanks, I somehow missed your earlier msg but do agree with your points on using 0.0.0.0 within container for default bridge network. I don’t think I did a good job of explaining the error I was facing from this block of code new TcpTransport(String, int, int, int)
where passing 0.0.0.0 for string does not work when switching to containers. Maybe accepting either IP/hostname would do the trick. Thanks for your prompt response! -----Original Message----- From: Stefan Seelmann (JIRA) [mailto:[email protected]] Sent: Monday, March 20, 2017 4:29 PM To: [email protected] Subject: [jira] [Commented] (DIRSERVER-2182) Apaches 2.0.0-M23 embedded instance cannot run correctly within docker container [ 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) The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting the email and its attachments from all computers without copying or disclosing it.
