Replies: 2 comments 3 replies
-
Hi, Valkey docker image would not be a drop in for Can you please try adding your configurations using this section - Additionally, If you want to use your own valkey.conf ...from here: https://hub.docker.com/r/valkey/valkey |
Beta Was this translation helpful? Give feedback.
-
Also @roshkhatri to me the documentation option doesnt work if I want to still have the data volume also attached (again a thing that works on redis). If I attempt both volumes the docker starts but is unreachable. Here are the steps to reproduce: docker pull valkey/valkey:7.2.5 mkdir /var/lib/docker/volumes/valkey-data/conf docker run -d -v /valkey-data/:/data -v /var/lib/docker/volumes/valkey-data/conf:/usr/local/etc/valkey --name valkey -p 6379:6379 --memory=4g --cpus=8 valkey/valkey:7.2.5 valkey-server /usr/local/etc/valkey/valkey.conf |
Beta Was this translation helpful? Give feedback.
-
Hi,
With Redis docker you could send certain params in the RUN command:
docker run -e REDIS_ARGS='--maxmemory 4gb --maxmemory-policy allkeys-lfu' -p 6379:6379 redis/redis-stack:latest
I attempted the same on the new valkey with both REDIS_ARGS and VALKEY_ARGS
docker run -e REDIS_ARGS='--maxmemory 4gb --maxmemory-policy allkeys-lfu' -p 6379:6379 valkey/valkey:7.2.5
But when I run CLI config get maxmemory or config get maxmemory-policy they are 0 and noeviction
How can I set them persistently (not by config set as they are removed after docker restart) on the new valkey docker ?
Beta Was this translation helpful? Give feedback.
All reactions