Process: 129 ExecStartPre=/usr/libexec/dirsrv/ds_systemd_ask_password_acl /etc/dirsrv/slapd-companytest/dse.ldif (code=exited, status=0/SUCCESS) - 389 Directory Server companytest.ĭrop-In: active (running) since Tue 09:48:48 UTC 1min 51s ago.Mar 07 10:12:01 728da1863072 systemd: Failed to start 389 Directory Server companytest. Mar 07 10:12:01 728da1863072 systemd: Control process exited, code=exited, status=1/FAILURE Mar 07 10:12:01 728da1863072 ds_systemd_ask_password_acl: setfacl: /var/run/systemd/ask-password: Operation not supported Mar 07 10:12:01 728da1863072 systemd: Starting 389 Directory Server companytest. Process: 490 ExecStartPre=/usr/libexec/dirsrv/ds_systemd_ask_password_acl /etc/dirsrv/slapd-companytest/dse.ldif (code=exited, statu> Loaded: loaded enabled vendor preset: disabled)ĭrop-In: failed (Result: exit-code) since Tue 10:12:01 UTC 4min 26s ago Here’s the result I get in terminal container with command systemctl status in macOS. Here’s my repo to reproduce the container: libreto/almalinux-389-ds at main So far the container runs well in Windows WSL2 but it fails in macOS. I create a AlmaLinux 9 389 Directory Server container to make me easier interact with LDAP server via Web UI (Cockpit).
Reference link: Docker macOS (Apple Silicon): ds_systemd_ask_password_acl: setfacl: /var/run/systemd/ask-password: Operation not supported The problem comes from ds_systemd_ask_password_acl.
0 kommentar(er)
