diff --git a/bitnami/neo4j/2026/debian-12/Dockerfile b/bitnami/neo4j/2026/debian-12/Dockerfile index 6194c3287a4e..3cc7750520c1 100644 --- a/bitnami/neo4j/2026/debian-12/Dockerfile +++ b/bitnami/neo4j/2026/debian-12/Dockerfile @@ -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-02-19T03:16:07Z" \ + org.opencontainers.image.created="2026-03-06T15:37:27Z" \ 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.1.4" + org.opencontainers.image.version="2026.2.2" ENV HOME="/opt/bitnami/neo4j/.home" \ OS_ARCH="${TARGETARCH:-amd64}" \ @@ -30,7 +30,7 @@ RUN --mount=type=secret,id=downloads_url,env=SECRET_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.1.4-0-linux-${OS_ARCH}-debian-12" \ + "neo4j-2026.2.2-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.1.4" \ +ENV APP_VERSION="2026.2.2" \ 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" diff --git a/bitnami/neo4j/README.md b/bitnami/neo4j/README.md index 386d94804ed9..b40971cc0b2d 100644 --- a/bitnami/neo4j/README.md +++ b/bitnami/neo4j/README.md @@ -1,7 +1,5 @@ # Bitnami Secure Image for Neo4j -## What is Neo4j? - > Neo4j is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions. [Overview of Neo4j](https://www.neo4j.org/) @@ -9,6 +7,8 @@ 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 ``` @@ -58,6 +58,10 @@ cd bitnami/APP/VERSION/OPERATING-SYSTEM docker build -t bitnami/APP:latest . ``` +## 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. @@ -66,80 +70,22 @@ For persistence you should mount a volume at the `/bitnami` path. The above exam To avoid inadvertent removal of this volume you can [mount host directories as data volumes](https://docs.docker.com/engine/tutorials/dockervolumes/). Alternatively you can make use of volume plugins to host the volume data. -```console -docker run -v /path/to/neo4j-persistence:/bitnami bitnami/neo4j:latest -``` - -or by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/neo4j/docker-compose.yml) file present in this repository: - -```yaml -neo4j: - ... - volumes: - - /path/to/neo4j-persistence:/bitnami - ... -``` - -> NOTE: As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`. +> **NOTE** As this is a non-root container, the mounted files and directories must have the proper permissions for the UID `1001`. ## Connecting to other containers Using [Docker container networking](https://docs.docker.com/engine/userguide/networking/), a different server running inside a container can easily be accessed by your application containers and vice-versa. -Containers attached to the same network can communicate with each other using the container name as the hostname. - -### Using the Command Line - -#### Step 1: Create a network - -```console -docker network create neo4j-network --driver bridge -``` - -#### Step 2: Launch the Neo4j container within your network - -Use the `--network ` argument to the `docker run` command to attach the container to the `neo4j-network` network. - -```console -docker run --name neo4j-node1 --network neo4j-network bitnami/neo4j:latest -``` - -#### Step 3: Run another containers - -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 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. - -```yaml -version: '2' - -networks: - neo4j-network: - driver: bridge - -services: - neo4j: - image: bitnami/neo4j:latest - networks: - - neo4j-network - ports: - - 7474:7474 - - 7473:7473 - - 7687:7687 -``` - -Then, launch the containers using: - -```console -docker-compose up -d -``` +Containers attached to the same network can communicate with each other using the container name as the host name. ## Configuration +The following sections describe environment variables and related settings. + ### Environment variables +The following tables list the main variables you can set. + #### Customizable environment variables | Name | Description | Default Value | @@ -189,56 +135,14 @@ docker-compose up -d 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. -#### Specifying Environment Variables 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: - -```yaml -neo4j: - ... - environment: - - NEO4J_BOLT_PORT_NUMBER=7777 - ... -``` - -#### Specifying Environment Variables on the Docker command line - -```console -docker run -d -e NEO4J_BOLT_PORT_NUMBER=7777 --name neo4j bitnami/neo4j:latest -``` - ### 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`. -#### 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: - -```yaml -neo4j: - ... - volumes: - - /local/path/to/your/confDir:/bitnami/neo4j/conf - ... -``` - ### Adding extra Neo4j plugins In order to add extra plugins, 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/plugins`. -#### Using Docker Compose to add plugins - -Modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/neo4j/docker-compose.yml) file present in this repository: - -```yaml -neo4j: - ... - volumes: - - /local/path/to/your/plugins:/bitnami/neo4j/plugins - ... -``` - ### FIPS configuration in Bitnami Secure Images The Bitnami Neo4j Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables: @@ -261,74 +165,13 @@ 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. -## Maintenance +## Notable changes -### Upgrade this image - -Bitnami provides up-to-date versions of neo4j, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container. - -#### Step 1: Get the updated image - -```console -docker pull bitnami/neo4j:latest -``` - -or if you're using Docker Compose, update the value of the image property to -`bitnami/neo4j:latest`. - -#### Step 2: Stop and backup the currently running container - -Stop the currently running container using the command - -```console -docker stop neo4j -``` - -or using Docker Compose: - -```console -docker-compose stop neo4j -``` - -Next, take a snapshot of the persistent volume `/path/to/neo4j-persistence` using: - -```console -rsync -a /path/to/neo4j-persistence /path/to/neo4j-persistence.bkp.$(date +%Y%m%d-%H.%M.%S) -``` - -You can use this snapshot to restore the database state should the upgrade fail. - -#### Step 3: Remove the currently running container - -```console -docker rm -v neo4j -``` - -or using Docker Compose: - -```console -docker-compose rm -v neo4j -``` - -#### Step 4: Run the new image - -Re-create your container from the new image, restoring your backup if necessary. - -```console -docker run --name neo4j bitnami/neo4j:latest -``` - -or using Docker Compose: - -```console -docker-compose up neo4j -``` - -## Notable Changes +The following subsections describe notable changes. ### 4.3.0-debian-10-r17 -- Decrease the size of the container. The configuration logic is now based on Bash scripts in the `rootfs/` folder. In addition to this, the container now has the latest stable version of the [apoc library](https://github.com/neo4j-contrib/neo4j-apoc-procedures) enabled by default. +- Decrease the size of the container. The configuration logic is now based on Bash scripts in the `rootfs/` folder. In addition to this, the container now has the latest stable version of the [`apoc` library](https://github.com/neo4j-contrib/neo4j-apoc-procedures) enabled by default. - Now the configuration file is not persisted, so it is recommended to remove the persisted file in `/bitnami/neo4j/conf/` to avoid potential upgrade issues. @@ -336,12 +179,6 @@ docker-compose up neo4j - The Neo4j container has been migrated to a non-root user approach. Previously the container ran as the `root` user and the Neo4j daemon was started as the `neo4j` user. From now on, both the container and the Neo4j daemon run as user `1001`. As a consequence, the data directory must be writable by that user. You can revert this behavior by changing `USER 1001` to `USER root` in the Dockerfile. -## 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. - -If you detect any issue in the `docker-compose.yaml` file, feel free to report it or contribute with a fix by following our [Contributing Guidelines](https://github.com/bitnami/containers/blob/main/CONTRIBUTING.md). - ## License Copyright © 2026 Broadcom. The term "Broadcom" refers to Broadcom Inc. and/or its subsidiaries.