[bitnami/harbor-portal] Release 2.10.1-debian-12-r1 (#64336)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-03-31 19:26:26 +02:00
committed by GitHub
parent cd81324f45
commit 4ec53e0e84
2 changed files with 7 additions and 2 deletions

View File

@@ -7,10 +7,10 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:c50c90cfd9d12b445b011e6ad529f1ad3daea45c26d20b00732fae3cd71f6a83" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2024-03-15T09:55:12Z" \
org.opencontainers.image.created="2024-03-31T16:40:00Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="2.10.1-debian-12-r0" \
org.opencontainers.image.ref.name="2.10.1-debian-12-r1" \
org.opencontainers.image.title="harbor-portal" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="2.10.1"

View File

@@ -164,6 +164,11 @@ nginx_validate() {
nginx_initialize() {
info "Initializing NGINX"
# bypassing the setup.sh logic. If the file already exists do not overwrite (in
# case someone mounts a configuration file in /opt/bitnami/nginx/conf)
debug "Copying files from $NGINX_DEFAULT_CONF_DIR to $NGINX_CONF_DIR"
cp -nr "$NGINX_DEFAULT_CONF_DIR"/. "$NGINX_CONF_DIR" || true
# This fixes an issue where the trap would kill the entrypoint.sh, if a PID was left over from a previous run
# Exec replaces the process without creating a new one, and when the container is restarted it may have the same PID
rm -f "${NGINX_TMP_DIR}/nginx.pid"