The containers have a pretty bad entropy level so the KDC won't start because of this. We can overcome this by using `/dev/urandom` which is less secure but does not care about entropy.
Obviously, this Kerberos container has to be run on the same network as the ldap container or make it possible to reach the outsider LDAP server. For the former case,
I suggest for you to use my compatible LDAP docker with Kerberos image `nugaon/openldap-with-kerberos`,
that you can find on [GitHub](https://github.com/nugaon/docker-openldap-with-kerberos) as well.
| `SEARCH_DOMAINS` | domain suffix search list | example.com |
| `LDAP_DC` | domain suffix search list | dc=example,dc=com |
| `LDAP_USER` | ldap service user | admin |
| `LDAP_PASS` | ldap service pass | admin |
| `LDAP_URL` | ldap url | ldap://ldap |
# Bind LDAP user to Kerberos DB
If you add new users in LDAP you have to register them in Kerberos as well in order to utilize Kerberos authentication. It is possible by the following command: