Readme.md should cover the case of an ldap server that is accessible outside the container

[kbuchsicf]

I found simply adding "-network host" to docker run was sufficient, but maybe there is a better method or best practice. Having it accessible outside the container IS the purpose of running openldap, isn't it?

[n9yty]

I'm just starting with Docker, but it seems that you have to read some about Docker if you are going to use a project like this... Use port mapping if you want to control which port on localhost gets mapped to a port in the container. It seems this is outside the scope of what should be covered in a particular Docker project, it is common to all work with containers. You can do this with -p{localhostport}:{containerport} on the run command line, or specify it in a docker-compose.yml file if you are running it that way. Maybe I'm missing something, but I think this is what you want.

[kbuchsicf]

I wouldn't think of it as general education on how to use docker. Rather it is about how to use this container. For example, compare https://hub.docker.com/_/httpd/
where it says:

If you don't want to include a Dockerfile in your project, it is sufficient to do the following:
$ docker run -dit --name my-apache-app -p 8080:80 -v "$PWD":/usr/local/apache2/htdocs/...

Since this is more of a container that is run standalone, not typically one you would include in a Dockerfile, I would believe the above would be an example of the main use case.