2.6.1-debian-10-r72 release
This commit is contained in:
parent
00945dde62
commit
250ccb0c71
|
|
@ -19,7 +19,7 @@ COPY rootfs /
|
|||
RUN /opt/bitnami/scripts/openldap/postunpack.sh
|
||||
ENV APP_VERSION="2.6.1" \
|
||||
BITNAMI_APP_NAME="openldap" \
|
||||
BITNAMI_IMAGE_VERSION="2.6.1-debian-10-r71" \
|
||||
BITNAMI_IMAGE_VERSION="2.6.1-debian-10-r72" \
|
||||
PATH="/opt/bitnami/openldap/bin:/opt/bitnami/openldap/sbin:/opt/bitnami/common/bin:$PATH"
|
||||
|
||||
EXPOSE 1389 1636
|
||||
|
|
|
|||
|
|
@ -549,4 +549,4 @@ olcTLSDHParamFile: $LDAP_TLS_DH_PARAMS_FILE
|
|||
EOF
|
||||
fi
|
||||
debug_execute ldapmodify -Y EXTERNAL -H "ldapi:///" -f "${LDAP_SHARE_DIR}/certs.ldif"
|
||||
}
|
||||
}
|
||||
|
|
@ -41,7 +41,7 @@ Non-root container images add an extra layer of security and are generally recom
|
|||
Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
|
||||
|
||||
|
||||
* [`2.6`, `2.6-debian-10`, `2.6.1`, `2.6.1-debian-10-r71`, `latest` (2.6/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-openldap/blob/2.6.1-debian-10-r71/2.6/debian-10/Dockerfile)
|
||||
* [`2.6`, `2.6-debian-10`, `2.6.1`, `2.6.1-debian-10-r72`, `latest` (2.6/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-openldap/blob/2.6.1-debian-10-r72/2.6/debian-10/Dockerfile)
|
||||
* [`2.5`, `2.5-debian-10`, `2.5.11`, `2.5.11-debian-10-r73` (2.5/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-openldap/blob/2.5.11-debian-10-r73/2.5/debian-10/Dockerfile)
|
||||
|
||||
Subscribe to project updates by watching the [bitnami/openldap GitHub repo](https://github.com/bitnami/bitnami-docker-openldap).
|
||||
|
|
@ -185,7 +185,7 @@ The Bitnami Docker OpenLDAP can be easily setup with the following environment v
|
|||
- `LDAP_PASSWORDS`: Comma separated list of passwords to use for LDAP users. Default: **bitnami1,bitnami2**
|
||||
- `LDAP_USER_DC`: DC for the users' organizational unit. Default: **users**
|
||||
- `LDAP_GROUP`: Group used to group created users. Default: **readers**
|
||||
- `LDAP_ADD_SCHEMAS`: Whether to add the schemas specified in `LDAP_EXTRA_SCHEMAS`. Default: **yes**
|
||||
- `LDAP_ADD_SCHEMAS`: Whether to add the schemas specified in `LDAP_EXTRA_SCHEMAS`. Default: **yes**
|
||||
- `LDAP_EXTRA_SCHEMAS`: Extra schemas to add, among OpenLDAP's distributed schemas. Default: **cosine, inetorgperson, nis**
|
||||
- `LDAP_SKIP_DEFAULT_TREE`: Whether to skip creating the default LDAP tree based on `LDAP_USERS`, `LDAP_PASSWORDS`, `LDAP_USER_DC` and `LDAP_GROUP`. Please note that this will **not** skip the addition of schemas or importing of LDIF files. Default: **no**
|
||||
- `LDAP_CUSTOM_LDIF_DIR`: Location of a directory that contains LDIF files that should be used to bootstrap the database. Only files ending in `.ldif` will be used. Default LDAP tree based on the `LDAP_USERS`, `LDAP_PASSWORDS`, `LDAP_USER_DC` and `LDAP_GROUP` will be skipped when `LDAP_CUSTOM_LDIF_DIR` is used. When using this it will override the usage of `LDAP_USERS`, `LDAP_PASSWORDS`, `LDAP_USER_DC` and `LDAP_GROUP`. You should set `LDAP_ROOT` to your base to make sure the `olcSuffix` configured on the database matches the contents imported from the LDIF files. Default: **/ldifs**
|
||||
|
|
|
|||
Loading…
Reference in New Issue