From 3af24ce63a553f093c076746e45069cd2d0b7ef8 Mon Sep 17 00:00:00 2001 From: Marisa Date: Tue, 4 Nov 2025 14:55:24 -0500 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c3b0094..6d938da 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ If you just want to jump in the container and right now don't care saving the co ``` If you wish (and it is recommended in development) to save the configuration and LDAP directory structure (also called LDAP database) outside of the container, run this command instead: ``` -> docker run -h example.com -i -p 389:389 -t ldapdock -v ldap_data:/var/lib/ldap -v ldap_config:/etc/ldap/slapd.d +> docker run -h example.com -i -p 389:389 -p 639:639 -t -v ldap_data:/var/lib/ldap -v ldap_config:/etc/ldap/slapd.d ldapdock ``` `Parameters explanation:`with -h we are specifying the name of the host, we are using example.com, this is very important. -i tells docker to run in an interactive way instead of running the container in the background. -t goes in hand with -i, and allocates a tty (terminal) so we can run commands. The parameter -p tells Docker it's the port our server will use. -v mounts a volume to save miscellaneous data in general, and config, content such as directories, databases and users.