From 8f1c8ffbb51de31df21ab0f98c43379ee6442da4 Mon Sep 17 00:00:00 2001
From: Bitnami Bot <bitnami-bot@vmware.com>
Date: Fri, 17 Feb 2023 19:34:48 +0100
Subject: [PATCH] [bitnami/neo4j] Release 4.4.17-debian-11-r5 (#24392)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
---
 bitnami/neo4j/4/debian-11/Dockerfile               | 14 +++++++-------
 .../opt/bitnami/.bitnami_components.json           | 12 ++++++------
 bitnami/neo4j/README.md                            |  4 ++--
 3 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/bitnami/neo4j/4/debian-11/Dockerfile b/bitnami/neo4j/4/debian-11/Dockerfile
index 1721fd4fa57c..5a8e6a0a9048 100644
--- a/bitnami/neo4j/4/debian-11/Dockerfile
+++ b/bitnami/neo4j/4/debian-11/Dockerfile
@@ -3,11 +3,11 @@ FROM docker.io/bitnami/minideb:bullseye
 ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
 ARG TARGETARCH
 
-LABEL org.opencontainers.image.authors="https://bitnami.com/contact" \
-      org.opencontainers.image.description="Application packaged by Bitnami" \
+LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
+      org.opencontainers.image.created="2023-02-17T18:03:28Z" \
+      org.opencontainers.image.description="Application packaged by VMware, Inc" \
       org.opencontainers.image.licenses="Apache-2.0" \
-      org.opencontainers.image.ref.name="4.4.17-debian-11-r4" \
-      org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/neo4j" \
+      org.opencontainers.image.ref.name="4.4.17-debian-11-r5" \
       org.opencontainers.image.title="neo4j" \
       org.opencontainers.image.vendor="VMware, Inc." \
       org.opencontainers.image.version="4.4.17"
@@ -23,9 +23,9 @@ SHELL ["/bin/bash", "-o", "pipefail", "-c"]
 RUN install_packages ca-certificates curl jq procps zlib1g
 RUN mkdir -p /tmp/bitnami/pkg/cache/ && cd /tmp/bitnami/pkg/cache/ && \
     COMPONENTS=( \
-      "java-11.0.18-10-0-linux-${OS_ARCH}-debian-11" \
-      "neo4j-4.4.17-0-linux-${OS_ARCH}-debian-11" \
-      "gosu-1.16.0-1-linux-${OS_ARCH}-debian-11" \
+      "java-11.0.18-10-1-linux-${OS_ARCH}-debian-11" \
+      "neo4j-4.4.17-1-linux-${OS_ARCH}-debian-11" \
+      "gosu-1.16.0-2-linux-${OS_ARCH}-debian-11" \
     ) && \
     for COMPONENT in "${COMPONENTS[@]}"; do \
       if [ ! -f "${COMPONENT}.tar.gz" ]; then \
diff --git a/bitnami/neo4j/4/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json b/bitnami/neo4j/4/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
index cc2e8fc483dd..68b95485c8aa 100644
--- a/bitnami/neo4j/4/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
+++ b/bitnami/neo4j/4/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
@@ -1,23 +1,23 @@
 {
     "gosu": {
         "arch": "amd64",
-        "digest": "9ab9654690d90d3c49ff66fb1eb286487e318adc899d036bc45922f6b176865b",
+        "digest": "f6056076afb745fd7d9d87d20f71e7248d63330352cf5ae0be2130b7f44a8cfa",
         "distro": "debian-11",
         "type": "NAMI",
-        "version": "1.16.0-1"
+        "version": "1.16.0-2"
     },
     "java": {
         "arch": "amd64",
-        "digest": "f8c3013925073f94edc495584b76f0b08c867ba35c524e2b262e47e815a443b9",
+        "digest": "cd40a6df619d734d300324ad671f34323152e84682bc998da1330f1a7f0acfa6",
         "distro": "debian-11",
         "type": "NAMI",
-        "version": "11.0.18-10-0"
+        "version": "11.0.18-10-1"
     },
     "neo4j": {
         "arch": "amd64",
-        "digest": "5798ae30a7ced4263f423c8a8a239437522e7b6df57dc33e877a01e76ed0541b",
+        "digest": "95cfc50d509b15da69c262687001d1d7734cbdfb1d134c8a85b902ec69f9c6ec",
         "distro": "debian-11",
         "type": "NAMI",
-        "version": "4.4.17-0"
+        "version": "4.4.17-1"
     }
 }
\ No newline at end of file
diff --git a/bitnami/neo4j/README.md b/bitnami/neo4j/README.md
index f52e46d2bad1..8c363c3f6ef0 100644
--- a/bitnami/neo4j/README.md
+++ b/bitnami/neo4j/README.md
@@ -112,7 +112,7 @@ docker run --name neo4j-node1 --network neo4j-network bitnami/neo4j:latest
 
 We can launch another containers using the same flag (`--network NETWORK`) in the `docker run` command. If you also set a name to your container, you will be able to use it as hostname in your network.
 
-### Using Docker Compose
+### Using a Docker Compose file
 
 When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named neo4j-network.
 
@@ -178,7 +178,7 @@ docker run -d -e NEO4J_BOLT_PORT_NUMBER=7777 --name neo4j bitnami/neo4j:latest
 
 In order to load your own configuration files, you will have to make them available to the container. You can do it mounting a [volume](https://docs.docker.com/engine/tutorials/dockervolumes/) in `/bitnami/neo4j/conf`.
 
-#### Using Docker Compose to add a custom config file
+#### Using Docker Compose
 
 Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/neo4j/docker-compose.yml) file present in this repository: