docker-keepalived VS docker-openldap

For this you are right. If that IP isnt available then your cluster wouldnt be reachable. So you counter this by having the nodes create they're own ip that can be shared. I have my nodes on 10.0.1.10-15, and i use a Keepalived (check here and herefor info) service to claim 10.0.1.5 and use that as the target for my forwarding. It works by designating a "master" which claims the ip and having other slaves running on the other (specifically manager) nodes. When they lose connection to the master, another takes the role, claims the IP from the DHCP server and starts accepting the traffic. The equivalent in kubernetes is MetalLB i believe, for those that are interested.

I'm entirely unfamiliar with overlays. I don't believe I've configured any on my OpenLDAP server, as it is just a default docker image I've populated with some OUs and users.

I'm trying to integrate LDAP into my small homelab but I'm extreme noobie in it. So far I've tried: 1. OpenLDAP - not so resource heavy but I found it difficult go get working correctly with NextCloud, Keycloak and Jellyfin. Maybe someone could recommend an easy to follow guide? 2. LLDAP - honestly it's almost prefect. Nice clean UI, great guides how to setup with everything I need, but it's a read-only LDAP, so I cannot create or manage users with Keycloak or NC, that's about the only downside and probably bugs me more than it should. 3. 389ds - has everything I need (and probably some more), super easy to setup with this guide but the elephant in the room is that it uses 700MiB of RAM (whereas LLDAP uses only 7-8MiB). That's a big difference which really makes me question whether I want to use this particular solution.

I have been struggling for a week to get sudo to work with my LDAP setup. I am using this docker setup. I have added these attributes to my server.

Hi, I've used the osixia github repository to spin up a docker container act as a LDAP Slave and I've successfully used the custom configuration and spin up the container. When i checked the logs of the container i saw the following as the output when it tries to sync with the Master.

It is quite straightforward to stand up an LDAP server listening in plaintext. My favorite mechanism is using the openldap container, although there are other options.

I'm trying to setup a LDAP server using the Osixia Docker container through docker-compose. I want it to contain lists of PosixAccount and PosixGroups, and use them to grant access to some external applications which also have a simpleSecurityObject entry in the directory (e.g. Grafana, which I already integrated with another LDAP server).

I've been trying to setup an openldap server from https://github.com/osixia/docker-openldap

I've grown quite tired of how painful it is to manage my LDAP server with multi-master replication. Currently I'm running osixia/openldap, with a wheelybird/ldap-user-manager frontend to manage users, all hosted on my Kubernetes cluster. Eventually, I'm looking to migrate to nitnelave/lldap