Skip to content

fix: Update Valkey image source in docker-compose #2060

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
asterixix wants to merge 1 commit into
base: staging
Choose a base branch
from
+1 −1
Draft

fix: Update Valkey image source in docker-compose #2060

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docker-compose.db.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ services:

valkey:
container_name: zerodotemail-redis
image: docker.io/bitnami/valkey:8.0
image: valkey/valkey:8.0
environment:
Comment on lines +18 to 19
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After switching to valkey/valkey, the current volume target path under /bitnami/valkey/data is very likely no longer the correct data directory, which can break persistence (data written elsewhere in the container won’t be stored in the named volume). Update the mount to the official image’s data dir (commonly /data) or whatever path the image documents.

Copilot uses AI. Check for mistakes.
- ALLOW_EMPTY_PASSWORD=yes
- VALKEY_DISABLE_COMMANDS=FLUSHDB,FLUSHALL
Expand Down
Loading