[GH-ISSUE #300] Install via docker issue #114

New issue

Closed

opened 2026-02-27 08:15:19 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 08:15:19 +03:00

Owner

Originally created by @slushfall on GitHub (Sep 19, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/300

Fresh install Ubuntu 20.04.

What could be the reason of db errors while starting docker container?

#docker run nitnelave/lldap
Unable to find image 'nitnelave/lldap:latest' locally
latest: Pulling from nitnelave/lldap
213ec9aee27d: Pull complete
425b0f2fef8f: Pull complete
ab9a9bfc820f: Pull complete
fed2c8be76d2: Pull complete
d3214953ac8b: Pull complete
492eed7e4563: Pull complete
4f4fb700ef54: Pull complete
Digest: sha256:977f1d2c26c108e1214d9e75f0a1413f4cda617a4f8eceba771739cc820b713b
Status: Downloaded newer image for nitnelave/lldap:latest
[entrypoint] Copying the default config to /data/lldap_config.toml
[entrypoint] Edit this file to configure LLDAP.

Setup permissions..
Starting lldap..

Loading configuration from /data/lldap_config.toml
WARNING: Default JWT secret used! This is highly unsafe and can allow attackersto log in as admin.
WARNING: Unsecure default admin password is used.
2022-09-19T12:28:45.715217229+00:00 INFO set_up_server [ 228ms | 100.00% ]
2022-09-19T12:28:45.715264689+00:00 INFO ┝━ ｉ [info]: Starting LLDAP version 0.4.0
2022-09-19T12:28:45.725360680+00:00 ERROR ┝━ 🚨 [error]: | error: Database error: no rows returned by a query that expected to return at least one row
2022-09-19T12:28:45.725368259+00:00 WARN ┝━ 🚧 [warn]: Could not get admin user, trying to create it: Database error: no rows returned by a query that expected to return at least one row
2022-09-19T12:28:45.947484357+00:00 WARN ┝━ 🚧 [warn]: Could not find password_manager group, trying to create it

Originally created by @slushfall on GitHub (Sep 19, 2022). Original GitHub issue: https://github.com/lldap/lldap/issues/300 Fresh install Ubuntu 20.04. What could be the reason of db errors while starting docker container? #docker run nitnelave/lldap Unable to find image 'nitnelave/lldap:latest' locally latest: Pulling from nitnelave/lldap 213ec9aee27d: Pull complete 425b0f2fef8f: Pull complete ab9a9bfc820f: Pull complete fed2c8be76d2: Pull complete d3214953ac8b: Pull complete 492eed7e4563: Pull complete 4f4fb700ef54: Pull complete Digest: sha256:977f1d2c26c108e1214d9e75f0a1413f4cda617a4f8eceba771739cc820b713b Status: Downloaded newer image for nitnelave/lldap:latest [entrypoint] Copying the default config to /data/lldap_config.toml [entrypoint] Edit this file to configure LLDAP. > Setup permissions.. > Starting lldap.. Loading configuration from /data/lldap_config.toml WARNING: Default JWT secret used! This is highly unsafe and can allow attackersto log in as admin. WARNING: Unsecure default admin password is used. 2022-09-19T12:28:45.715217229+00:00 INFO set_up_server [ 228ms | 100.00% ] 2022-09-19T12:28:45.715264689+00:00 INFO ┝━ ｉ [info]: Starting LLDAP version 0.4.0 2022-09-19T12:28:45.725360680+00:00 ERROR ┝━ 🚨 [error]: | error: Database error: `no rows returned by a query that expected to return at least one row` 2022-09-19T12:28:45.725368259+00:00 WARN ┝━ 🚧 [warn]: Could not get admin user, trying to create it: Database error: `no rows returned by a query that expected to return at least one row` 2022-09-19T12:28:45.947484357+00:00 WARN ┝━ 🚧 [warn]: Could not find password_manager group, trying to create it

kerem closed this issue

2026-02-27 08:15:19 +03:00

kerem commented

2026-02-27 08:15:19 +03:00

Author

Owner

@nitnelave commented on GitHub (Sep 19, 2022):

I think it's just the one-time setup code that is a bit too greedy to log. If you restart the container, now that it has created the DB, it should work fine.

@nitnelave commented on GitHub (Sep 19, 2022): I think it's just the one-time setup code that is a bit too greedy to log. If you restart the container, now that it has created the DB, it should work fine.

kerem commented

2026-02-27 08:15:19 +03:00

Author

Owner

@nitnelave commented on GitHub (Sep 30, 2022):

Ideally we could just downgrade the log rather than remove it if https://github.com/tokio-rs/tracing/issues/2330 is accepted.

@nitnelave commented on GitHub (Sep 30, 2022): Ideally we could just downgrade the log rather than remove it if https://github.com/tokio-rs/tracing/issues/2330 is accepted.

kerem referenced this issue

2026-02-27 08:17:57 +03:00

[PR #117] [MERGED] ldap_handler: trim spaces in LDAP identifiers #550