Bitnami/containers
2
0
Fork 0
mirror of https://github.com/bitnami/containers.git synced 2026-03-21 15:29:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/neo4j] Release 4.4.29-debian-11-r2 (#55087)

Browse Source 
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-01-20 02:28:09 +01:00
committed by GitHub
parent b1babb8da2
commit 48418243ae
3 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
bitnami/neo4j/4/debian-11/Dockerfile
View File

@@ -8,10 +8,10 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \ LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \ org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2024-01-11T15:47:27Z" \ org.opencontainers.image.created="2024-01-20T00:26:37Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \ org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \ org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="4.4.29-debian-11-r1" \ org.opencontainers.image.ref.name="4.4.29-debian-11-r2" \
org.opencontainers.image.title="neo4j" \ org.opencontainers.image.title="neo4j" \
org.opencontainers.image.vendor="VMware, Inc." \ org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="4.4.29" org.opencontainers.image.version="4.4.29"
@@ -27,7 +27,7 @@ SHELL ["/bin/bash", "-o", "errexit", "-o", "nounset", "-o", "pipefail", "-c"]
RUN install_packages ca-certificates curl jq procps zlib1g RUN install_packages ca-certificates curl jq procps zlib1g
RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
COMPONENTS=( \ COMPONENTS=( \
"java-11.0.21-10-6-linux-${OS_ARCH}-debian-11" \ "java-11.0.22-12-0-linux-${OS_ARCH}-debian-11" \
"neo4j-4.4.29-0-linux-${OS_ARCH}-debian-11" \ "neo4j-4.4.29-0-linux-${OS_ARCH}-debian-11" \
) ; \ ) ; \
for COMPONENT in "${COMPONENTS[@]}"; do \ for COMPONENT in "${COMPONENTS[@]}"; do \
@@ -43,6 +43,7 @@ RUN apt-get autoremove --purge -y curl && \
apt-get update && apt-get upgrade -y && \ apt-get update && apt-get upgrade -y && \
apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives
RUN chmod g+rwX /opt/bitnami RUN chmod g+rwX /opt/bitnami
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
COPY rootfs / COPY rootfs /
RUN /opt/bitnami/scripts/java/postunpack.sh RUN /opt/bitnami/scripts/java/postunpack.sh

2
bitnami/neo4j/4/debian-11/prebuildfs/opt/bitnami/.bitnami_components.json
View File

@@ -3,7 +3,7 @@
"arch": "amd64", "arch": "amd64",
"distro": "debian-11", "distro": "debian-11",
"type": "NAMI", "type": "NAMI",
"version": "11.0.21-10-6" "version": "11.0.22-12-0"
}, },
"neo4j": { "neo4j": {
"arch": "amd64", "arch": "amd64",

13
bitnami/neo4j/README.md
View File

@@ -13,13 +13,6 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
docker run --name neo4j bitnami/neo4j:latest docker run --name neo4j bitnami/neo4j:latest
``` ```
### Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/neo4j/docker-compose.yml > docker-compose.yml
docker-compose up -d
```
You can find the default credentials and available configuration options in the [Environment Variables](#environment-variables) section. You can find the default credentials and available configuration options in the [Environment Variables](#environment-variables) section.
## Why use Bitnami Images? ## Why use Bitnami Images?
@@ -328,6 +321,12 @@ 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. * 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).
## Contributing ## Contributing
We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution. We'd love for you to contribute to this container. You can request new features by creating an [issue](https://github.com/bitnami/containers/issues) or submitting a [pull request](https://github.com/bitnami/containers/pulls) with your contribution.