Remove VOLUME command

.test/tests/valkey-basics-persistent/run.sh

@@ -13,6 +13,13 @@ cid="$(docker run -d --name "$cname" --network "$network" "$image")"
 
 trap "docker rm -vf '$cid' >/dev/null; docker network rm '$network' >/dev/null" EXIT
 
+# Verify /data is not configured as a Docker volume
+volumes="$(docker inspect "$cname" --format '{{range .Mounts}}{{.Destination}} {{end}}')"
+if echo "$volumes" | grep -q "/data"; then
+  echo >&2 "ERROR: /data should not be a volume mount point"
+  exit 1
+fi
+
 valkey-cli() {
   docker run --rm -i \
     --network "$network" \

Dockerfile.template

@@ -176,7 +176,6 @@ RUN mkdir /data && \
 	chown valkey:valkey /data && \
 	valkey-cli --version && \
 	valkey-server --version
-VOLUME /data
 WORKDIR /data
 
 COPY docker-entrypoint.sh /usr/local/bin/

dockerhub-description-template.md

@@ -1,6 +1,3 @@
-## This file is auto-generated by the [Valkey-Release-Automation](https://github.com/valkey-io/valkey-release-automation/blob/main/.github/workflows/update-docker.yml) repository
-Last updated: {update_date}
-
 # Quick reference
 
 -	**Maintained by**:
@@ -41,7 +38,7 @@ $ docker run --name some-valkey -d valkey/valkey
 $ docker run --name some-valkey -d valkey/valkey valkey-server --save 60 1 --loglevel warning
 ```
 
-There are several different persistence strategies to choose from. This one will save a snapshot of the DB every 60 seconds if at least 1 write operation was performed (it will also lead to more logs, so the `loglevel` option may be desirable). If persistence is enabled, data is stored in the `VOLUME /data`, which can be used with `--volumes-from some-volume-container` or `-v /docker/host/dir:/data` (see [docs.docker volumes](https://docs.docker.com/engine/tutorials/dockervolumes/)).
+There are several different persistence strategies to choose from. This one will save a snapshot of the DB every 60 seconds if at least 1 write operation was performed (it will also lead to more logs, so the `loglevel` option may be desirable). If persistence is enabled, data is stored in the `/data` directory, which can be mounted using `-v /docker/host/dir:/data` (see [docs.docker volumes](https://docs.docker.com/engine/tutorials/dockervolumes/)).
 
 ## Connecting via `valkey-cli`
 

dockerhub-description.md

@@ -1,6 +1,3 @@
-## This file is auto-generated by the [Valkey-Release-Automation](https://github.com/valkey-io/valkey-release-automation/blob/main/.github/workflows/update-docker.yml) repository
-Last updated: 2025-07-07
-
 # Quick reference
 
 -	**Maintained by**:
@@ -51,7 +48,7 @@ $ docker run --name some-valkey -d valkey/valkey
 $ docker run --name some-valkey -d valkey/valkey valkey-server --save 60 1 --loglevel warning
 ```
 
-There are several different persistence strategies to choose from. This one will save a snapshot of the DB every 60 seconds if at least 1 write operation was performed (it will also lead to more logs, so the `loglevel` option may be desirable). If persistence is enabled, data is stored in the `VOLUME /data`, which can be used with `--volumes-from some-volume-container` or `-v /docker/host/dir:/data` (see [docs.docker volumes](https://docs.docker.com/engine/tutorials/dockervolumes/)).
+There are several different persistence strategies to choose from. This one will save a snapshot of the DB every 60 seconds if at least 1 write operation was performed (it will also lead to more logs, so the `loglevel` option may be desirable). If persistence is enabled, data is stored in the `/data` directory, which can be mounted using `-v /docker/host/dir:/data` (see [docs.docker volumes](https://docs.docker.com/engine/tutorials/dockervolumes/)).
 
 ## Connecting via `valkey-cli`