[GH-ISSUE #844] [BUG] Kubernetes: invalid value for ldap-port #304

New issue

Closed

opened 2026-02-27 08:16:32 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 08:16:32 +03:00

Owner

Originally created by @slaecker on GitHub (Feb 17, 2024).
Original GitHub issue: https://github.com/lldap/lldap/issues/844

Describe the bug
I'm trying to deploy lldap on my K3s cluster, but when the pod is starting it crashloops with the below error:

> Setup permissions..
> Starting lldap..

error: invalid value 'tcp://10.43.194.65:3890' for '--ldap-port <LDAP_PORT>': invalid digit found in string

I've tried setting LDAP_PORT to 3890 explicitly but the same error remains.

The deployment manifest:

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/name: lldap
  name: lldap
  namespace: auth
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: lldap
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app.kubernetes.io/name: lldap
    spec:
      containers:
      - image: lldap/lldap:stable
        name: lldap
        resources: {}
      restartPolicy: Always

Running the lldap image in podman works just fine.

To Reproduce
Steps to reproduce the behavior:

Deploy the above manifest to Kubernetes
Check the pod logs

Expected behavior
The pod starting and getting into a RUNNING state.

Logs

[entrypoint] Copying the default config to /data/lldap_config.toml
[entrypoint] Edit this file to configure LLDAP.
> Setup permissions..
> Starting lldap..

error: invalid value 'tcp://10.43.151.188:3890' for '--ldap-port <LDAP_PORT>': invalid digit found in string

For more information, try '--help'.

Additional context
K3s version: v1.28.5+k3s1

Originally created by @slaecker on GitHub (Feb 17, 2024). Original GitHub issue: https://github.com/lldap/lldap/issues/844 **Describe the bug** I'm trying to deploy lldap on my K3s cluster, but when the pod is starting it crashloops with the below error: ``` > Setup permissions.. > Starting lldap.. error: invalid value 'tcp://10.43.194.65:3890' for '--ldap-port <LDAP_PORT>': invalid digit found in string ``` I've tried setting `LDAP_PORT` to `3890` explicitly but the same error remains. The deployment manifest: ``` apiVersion: apps/v1 kind: Deployment metadata: labels: app.kubernetes.io/name: lldap name: lldap namespace: auth spec: replicas: 1 selector: matchLabels: app.kubernetes.io/name: lldap strategy: type: Recreate template: metadata: labels: app.kubernetes.io/name: lldap spec: containers: - image: lldap/lldap:stable name: lldap resources: {} restartPolicy: Always ``` Running the lldap image in podman works just fine. **To Reproduce** Steps to reproduce the behavior: 1. Deploy the above manifest to Kubernetes 2. Check the pod logs **Expected behavior** The pod starting and getting into a RUNNING state. **Logs** ``` [entrypoint] Copying the default config to /data/lldap_config.toml [entrypoint] Edit this file to configure LLDAP. > Setup permissions.. > Starting lldap.. error: invalid value 'tcp://10.43.151.188:3890' for '--ldap-port <LDAP_PORT>': invalid digit found in string For more information, try '--help'. ``` **Additional context** K3s version: v1.28.5+k3s1

kerem

2026-02-27 08:16:32 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 08:16:33 +03:00

Author

Owner

@nitnelave commented on GitHub (Feb 17, 2024):

Having never run any Kubernetes command ever, I'll be of limited help.

Where is the configuration for the service? Where does the value for the port come from?

What I can help with is this:

the env variable you're looking for is LLDAP_LDAP_PORT
command line arguments take precedence over env variables, so that might not help.

@nitnelave commented on GitHub (Feb 17, 2024): Having never run any Kubernetes command ever, I'll be of limited help. Where is the configuration for the service? Where does the value for the port come from? What I can help with is this: - the env variable you're looking for is LLDAP_LDAP_PORT - command line arguments take precedence over env variables, so that might not help.

kerem commented

2026-02-27 08:16:33 +03:00

Author

Owner

@slaecker commented on GitHub (Feb 17, 2024):

Thanks, setting LLDAP_LDAP_PORT did the trick. Strange though that this is needed. Never had such an issue before with any other image. If you ever need someone doing some Kubernetes testing let me know.

@slaecker commented on GitHub (Feb 17, 2024): Thanks, setting `LLDAP_LDAP_PORT` did the trick. Strange though that this is needed. Never had such an issue before with any other image. If you ever need someone doing some Kubernetes testing let me know.

kerem referenced this issue

2026-02-27 08:18:23 +03:00

[PR #304] [MERGED] server: Fix query building of chained ands/ors #667