389-ds
389 Directory Server container project.
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:firstyear/389-ds-container && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
Dockerfile | 0000000838 838 Bytes | |
nsswitch.conf | 0000000414 414 Bytes |
Latest Revision
William Brown (firstyear)
committed
(revision 22)
Add extra debug tools
Comments 5
Hi, can you place
ENV DS_DM_PASSWORD
alongside the other environment variables? Preferably, you can also place info about them in the README on dockerhub :)You can't have a bare
ENV VARIABLE
in a Dockerfile at build, it causes it to fail. However, I have updated the readme with all the options :) Hope that helps!when I use /data/config/container.inf, I set basedn = dc=example,dc=com, but I found it did not effect too.
This is not a tech support forum. Please don't use it as one. Use the 389-users mailing list.
Am I right by the finding that it is technically impossible to restore an offline backup (
dsctl localhost bak2db test4
from inside the container) due to the design of containers? Offline restore requires stopping 389-ds which is the main process; Hence container is killed.Maybe one can wrap a process around
/usr/sbin/ns-slapd
which keeps alive whiledsctl
does its work?