Hello everyone,
Issue: Docker communication to LDAP server happens through docker container private IP and not using host ip.
setup: Windows server 2022 (virtual machine - hyperV)
Linux container (wsl 2)
Currently, we see that the docker ip communicates directly to our LDAP server which eventually is rejected as docker private ip is not allowed to communicate with our company internal network.
While i see that windows 11/ linux VM works fine.
is there a way we can ensure container uses host ip for the communication.
while i used a workaround (port forwarding) for connection to ldap server and it works fine. I would like fix this so i can setup kerberoes and mount internal shared drives for which port forwarding may not be right solution.
Hi. I don’t even know how it is possible that LDAP sees the container IP as source. Linux containers are running in a virtual machine (WSL2 in your case) and the target is not supposed to see the actual container IPs. Similarly to how a server on the internet will not see your LAN IP as source.
So maybe it is something special Windows Server related.
I am not sure, but Docker Desktop is definitely not supported on Windows Servers and never was. I thought it also rejected installing it on Windows Servers.
Do I understand it correctly that you installed Windows Server itself in a virtual machine on a Windows host? That would mean you also running Docker Desktop in a virtual machine to run a virtual machine for the Docker daemon to run Linux containers.