public_git/bitnami-containers
1
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-10-18 01:42:21 +02:00
Code Issues Projects Releases Wiki Activity

[bitnami/neo4j] Release 2026.4.0-debian-12-r0 (#92611)

Browse Source 
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
2026-04-23 11:19:55 +02:00
committed by GitHub
parent 37fea78adb
commit 9169c006dd
2 changed files with 15 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitnami/neo4j/2026/debian-12/Dockerfile
+6 -6
View File
@@ -8,13 +8,13 @@ ARG JAVA_EXTRA_SECURITY_DIR="/bitnami/java/extra-security"
ARG TARGETARCH
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
org.opencontainers.image.created="2026-04-08T10:52:08Z" \
org.opencontainers.image.created="2026-04-23T08:52:49Z" \
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/neo4j/README.md" \
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/neo4j" \
org.opencontainers.image.title="neo4j" \
org.opencontainers.image.vendor="Broadcom, Inc." \
org.opencontainers.image.version="2026.3.1"
org.opencontainers.image.version="2026.4.0"
ENV HOME="/opt/bitnami/neo4j/.home" \
OS_ARCH="${TARGETARCH:-amd64}" \
@@ -29,8 +29,8 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_DOWNLOADS_URL \
DOWNLOADS_URL=${SECRET_DOWNLOADS_URL:-${DOWNLOADS_URL}} ; \
mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ || exit 1 ; \
COMPONENTS=( \
"jre-21.0.10-10-0-linux-${OS_ARCH}-debian-12" \
"neo4j-2026.3.1-0-linux-${OS_ARCH}-debian-12" \
"jre-21.0.11-11-0-linux-${OS_ARCH}-debian-12" \
"neo4j-2026.4.0-0-linux-${OS_ARCH}-debian-12" \
) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \
if [ ! -f "${COMPONENT}.tar.gz" ]; then \
@@ -50,9 +50,9 @@ RUN uninstall_packages curl
COPY rootfs /
RUN /opt/bitnami/scripts/java/postunpack.sh
RUN /opt/bitnami/scripts/neo4j/postunpack.sh
ENV APP_VERSION="2026.3.1" \
ENV APP_VERSION="2026.4.0" \
BITNAMI_APP_NAME="neo4j" \
IMAGE_REVISION="1" \
IMAGE_REVISION="0" \
JAVA_HOME="/opt/bitnami/java" \
JAVA_OPTS="-Duser.home=/opt/bitnami/neo4j/.home" \
PATH="/opt/bitnami/java/bin:/opt/bitnami/neo4j/bin:$PATH"
bitnami/neo4j/README.md
+9 -21
View File
@@ -7,14 +7,20 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
## TL;DR
Use this quick command to run the container.
```console
docker run --name neo4j bitnami/neo4j:latest
```
You can find the default credentials and available configuration options in the [Environment Variables](#environment-variables) section.
## Using `docker-compose.yml`
The docker-compose.yaml file of this container can be found in the [Bitnami Containers repository](https://github.com/bitnami/containers/).
[https://github.com/bitnami/containers/tree/main/bitnami/neo4j/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/neo4j/docker-compose.yml)
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/neo4j).
## Why use Bitnami Secure Images?
Those are hardened, minimal CVE images built and maintained by Bitnami. Bitnami Secure Images are based on the cloud-optimized, security-hardened enterprise [OS Photon Linux](https://vmware.github.io/photon/). Why choose BSI images?
@@ -40,10 +46,6 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
The Bitnami Neo4j Docker image is only available to [Bitnami Secure Images](https://bitnami.com) customers.
## Using `docker-compose.yaml`
Please be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes.
## Persisting your application
If you remove the container all your data and configurations will be lost, and the next time you run the image the database will be reinitialized. To avoid this loss of data, you should mount a volume that will persist even after the container is removed.
@@ -118,8 +120,6 @@ The following tables list the main variables you can set.
| `NEO4J_DAEMON_GROUP` | Neo4j system group. | `neo4j` |
| `JAVA_HOME` | Java installation folder. | `${BITNAMI_ROOT_DIR}/java` |
When you start the neo4j image, you can adjust the configuration of the instance by passing one or more environment variables either on the docker-compose file or on the `docker run` command line.
### Using your Neo4j configuration files
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`.
@@ -137,19 +137,7 @@ The Bitnami Neo4j Docker image from the [Bitnami Secure Images](https://go-vmwar
## Logging
The Bitnami neo4j Docker image sends the container logs to the `stdout`. To view the logs:
```console
docker logs neo4j
```
or using Docker Compose:
```console
docker-compose logs neo4j
```
You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
The Bitnami Neo4j Docker image sends the container logs to the `stdout`. You can configure the containers [logging driver](https://docs.docker.com/engine/admin/logging/overview/) using the `--log-driver` option if you wish to consume the container logs differently. In the default configuration docker uses the `json-file` driver.
## Notable changes