mirror of
https://github.com/bitnami/containers.git
synced 2026-10-17 18:23:14 +02:00
[bitnami/valkey] Release 9.0.4-debian-12-r0 (#92808)
Signed-off-by: Bitnami Bot <bitnami.bot@broadcom.com>
This commit is contained in:
Bitnami Bot
@@ -7,13 +7,13 @@ ARG DOWNLOADS_URL="downloads.bitnami.com/files/stacksmith"
|
||||
ARG TARGETARCH
|
||||
|
||||
LABEL org.opencontainers.image.base.name="docker.io/bitnami/minideb:bookworm" \
|
||||
org.opencontainers.image.created="2026-04-08T22:06:00Z" \
|
||||
org.opencontainers.image.created="2026-05-06T05:07:34Z" \
|
||||
org.opencontainers.image.description="Application packaged by Broadcom, Inc." \
|
||||
org.opencontainers.image.documentation="https://github.com/bitnami/containers/tree/main/bitnami/valkey/README.md" \
|
||||
org.opencontainers.image.source="https://github.com/bitnami/containers/tree/main/bitnami/valkey" \
|
||||
org.opencontainers.image.title="valkey" \
|
||||
org.opencontainers.image.vendor="Broadcom, Inc." \
|
||||
org.opencontainers.image.version="9.0.3"
|
||||
org.opencontainers.image.version="9.0.4"
|
||||
|
||||
ENV HOME="/" \
|
||||
OS_ARCH="${TARGETARCH:-amd64}" \
|
||||
@@ -29,7 +29,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=( \
|
||||
"wait-for-port-1.0.10-9-linux-${OS_ARCH}-debian-12" \
|
||||
"valkey-9.0.3-3-linux-${OS_ARCH}-debian-12" \
|
||||
"valkey-9.0.4-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/valkey/postunpack.sh
|
||||
ENV APP_VERSION="9.0.3" \
|
||||
ENV APP_VERSION="9.0.4" \
|
||||
BITNAMI_APP_NAME="valkey" \
|
||||
IMAGE_REVISION="4" \
|
||||
IMAGE_REVISION="0" \
|
||||
PATH="/opt/bitnami/common/bin:/opt/bitnami/valkey/bin:$PATH"
|
||||
|
||||
EXPOSE 6379
|
||||
|
||||
@@ -11,7 +11,13 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
|
||||
docker run --name valkey -e ALLOW_EMPTY_PASSWORD=yes bitnami/valkey:latest
|
||||
```
|
||||
|
||||
**Warning**: These quick setups are only intended for development environments. You are encouraged to change the insecure default credentials and check out the available configuration options in the [Configuration](#configuration) section for a more secure deployment.
|
||||
## 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/valkey/docker-compose.yml](https://github.com/bitnami/containers/tree/main/bitnami/valkey/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/valkey).
|
||||
|
||||
## Why use Bitnami Secure Images?
|
||||
|
||||
@@ -46,13 +52,9 @@ Learn more about the Bitnami tagging policy and the difference between rolling t
|
||||
|
||||
The Bitnami Valkey 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. For production-ready deployments, we highly recommend utilizing its associated [Bitnami Helm chart](https://github.com/bitnami/charts/tree/main/bitnami/valkey).
|
||||
|
||||
## Persisting your database
|
||||
|
||||
Valkey provides a different range of [persistence options](https://valkey.io/docs/topics/persistence.html). This contanier uses *AOF persistence by default* but it is easy to overwrite that configuration in a `docker-compose.yaml` file with this entry `command: /opt/bitnami/scripts/valkey/run.sh --appendonly no`. Alternatively, you may use the `VALKEY_AOF_ENABLED` env variable as explained in [Disabling AOF persistence](https://github.com/bitnami/containers/blob/main/bitnami/valkey#disabling-aof-persistence).
|
||||
Valkey provides a different range of [persistence options](https://valkey.io/docs/topics/persistence.html). This contanier uses *AOF persistence by default* but it is easy to overwrite that configuration by setting the following command when running the container `/opt/bitnami/scripts/valkey/run.sh --appendonly no`. Alternatively, you may use the `VALKEY_AOF_ENABLED` env variable as explained in [Disabling AOF persistence](https://github.com/bitnami/containers/blob/main/bitnami/valkey#disabling-aof-persistence).
|
||||
|
||||
If you remove the container all your data 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.
|
||||
|
||||
@@ -145,18 +147,6 @@ Passing extra command-line flags to the valkey service command is possible by ad
|
||||
docker run --name valkey -e ALLOW_EMPTY_PASSWORD=yes bitnami/valkey:latest /opt/bitnami/scripts/valkey/run.sh --maxmemory 100mb
|
||||
```
|
||||
|
||||
Alternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/valkey/docker-compose.yml) file present in this repository:
|
||||
|
||||
```yaml
|
||||
services:
|
||||
valkey:
|
||||
...
|
||||
environment:
|
||||
- ALLOW_EMPTY_PASSWORD=yes
|
||||
command: /opt/bitnami/scripts/valkey/run.sh --maxmemory 100mb
|
||||
...
|
||||
```
|
||||
|
||||
### Setting the server password on first run
|
||||
|
||||
Passing the `VALKEY_PASSWORD` environment variable when running the image for the first time will set the Valkey server password to the value of `VALKEY_PASSWORD` (or the content of the file specified in `VALKEY_PASSWORD_FILE`).
|
||||
@@ -181,19 +171,6 @@ Valkey offers [ACL](https://valkey.io/docs/topics/acl.html) which allows certain
|
||||
docker run -name valkey -e VALKEY_ACLFILE=/opt/bitnami/valkey/mounted-etc/users.acl -v /path/to/users.acl:/opt/bitnami/valkey/mounted-etc/users.acl bitnami/valkey:latest
|
||||
```
|
||||
|
||||
Alternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/valkey/docker-compose.yml) file present in this repository:
|
||||
|
||||
```yaml
|
||||
services:
|
||||
valkey:
|
||||
...
|
||||
environment:
|
||||
- VALKEY_ACLFILE=/opt/bitnami/valkey/mounted-etc/users.acl
|
||||
volumes:
|
||||
- /path/to/users.acl:/opt/bitnami/valkey/mounted-etc/users.acl
|
||||
...
|
||||
```
|
||||
|
||||
### Setting up a standalone instance
|
||||
|
||||
By default, this image is set up to launch Valkey in standalone mode on port 6379. Should you need to change this behavior, setting the `VALKEY_PORT_NUMBER` environment variable will modify the port number. This is not to be confused with `VALKEY_PRIMARY_PORT_NUMBER` or `VALKEY_REPLICA_PORT` environment variables that are applicable in replication mode.
|
||||
@@ -240,18 +217,6 @@ docker run --name valkey \
|
||||
bitnami/valkey:latest
|
||||
```
|
||||
|
||||
Alternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/valkey/docker-compose.yml) file present in this repository:
|
||||
|
||||
```yaml
|
||||
services:
|
||||
valkey:
|
||||
...
|
||||
volumes:
|
||||
- /path/to/your_valkey.conf:/opt/bitnami/valkey/mounted-etc/valkey.conf
|
||||
- /path/to/valkey-persistence:/bitnami/valkey/data
|
||||
...
|
||||
```
|
||||
|
||||
### Overriding configuration
|
||||
|
||||
Instead of providing a custom `valkey.conf`, you may also choose to provide only settings you wish to override. The image will look for `/opt/bitnami/valkey/mounted-etc/overrides.conf`. This will be ignored if custom `valkey.conf` is provided.
|
||||
@@ -263,17 +228,6 @@ docker run --name valkey \
|
||||
bitnami/valkey:latest
|
||||
```
|
||||
|
||||
Alternatively, modify the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/valkey/docker-compose.yml) file present in this repository:
|
||||
|
||||
```yaml
|
||||
services:
|
||||
valkey:
|
||||
...
|
||||
volumes:
|
||||
- /path/to/overrides.conf:/opt/bitnami/valkey/mounted-etc/overrides.conf
|
||||
...
|
||||
```
|
||||
|
||||
### Enable Valkey RDB persistence
|
||||
|
||||
When the value of `VALKEY_RDB_POLICY_DISABLED` is `no` (default value) the Valkey default persistence strategy will be used. If you want to modify the default strategy, you can configure it through the `VALKEY_RDB_POLICY` parameter.
|
||||
@@ -286,19 +240,7 @@ The Bitnami Valkey Docker image from the [Bitnami Secure Images](https://go-vmwa
|
||||
|
||||
## Logging
|
||||
|
||||
The Bitnami Valkey Docker image sends the container logs to the `stdout`. To view the logs:
|
||||
|
||||
```console
|
||||
docker logs valkey
|
||||
```
|
||||
|
||||
or using Docker Compose:
|
||||
|
||||
```console
|
||||
docker-compose logs valkey
|
||||
```
|
||||
|
||||
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 Valkey 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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user