LDAP outpost ingores "DOCKER_MAP_PORTS: false"

[BAAAASS]

Describe the bug
When I setup my LDAP Outpost container manually - as per the documenation and opt to use an external network. According to the docker documentation, when a external network is selected, then port mapping is disabled. I assign a static IP and try to connect to this IP on the original port 389, but it fails, connecting on 3389 does work.

To Reproduce
Create Outpost using this docker compose:
networks:
eth_lan:
external: true
auth_priv:
name: auth_priv
driver: bridge
ipam:
config:
- subnet: 172.19.1.0/24
Auth-LDAP:
container_name: Auth-LDAP
hostname: ldap.mypersonal.fqdn
image: ghcr.io/goauthentik/ldap:latest
restart: unless-stopped
networks:
auth_priv:
eth_lan:
ipv4_address: 192.168.40.8
environment:
DOCKER_MAP_PORTS: false
AUTHENTIK_HOST: https://auth.mypersonal.fqdn/
AUTHENTIK_INSECURE: false
AUTHENTIK_TOKEN: abcdefghijklmonpqrstuvwxyz1234567890

My primary certificate has the ldap.mypersonal.fqdn as a Subject Alternative Name on the same auth.mypersonal.fqdn certificate.
In the Outpost configuration, I have also configured the same flag: "DOCKER_MAP_PORTS: false"
The "eth_lan" is configured as an external network as an ipvlan

Expected behavior
Because of the flag that I specified in combination with the external network, I expec LDAP to listen on the default ports 389 and 636 instead of what it is currently doing and incorrectly listening on 3389 and 6636.

Version and Deployment (please complete the following information):
2024.10.1

[BAAAASS]

Adding to Docker-Compose:

cap_add:
__- NET_ADMIN
__- NET_RAW

Then, running:

sudo docker exec -u 0 -it Auth-LDAP bash
apt-get update
apt-get install iptables
iptables -t nat -A PREROUTING -p tcp --dport 389 -j REDIRECT --to-port 3389
iptables -t nat -A PREROUTING -p tcp --dport 636 -j REDIRECT --to-port 6636
su -c 'iptables-save > /etc/iptables/iptables.rules'

It does give me access via the normal 389 and 636 ports. However, this is not a propper solution.

[authentik-automation]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[BAAAASS]

This issue is still not resolved :-(

Automatically closing issues reported on GitHub, does not also automatically solve them :-(

[authentik-automation]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.