fix: Update Valkey image source in docker-compose

[asterixix]

Description

Starting in 2025, docker.io/bitnami/ tags were removed or migrated, so bitnami/valkey:8.0 simply no longer exists at that address. Using the official Valkey image.

---

Type of Change

Please delete options that are not relevant.

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature with breaking changes)
• 📝 Documentation update
• 🎨 UI/UX improvement
• 🔒 Security enhancement
• ⚡ Performance improvement

Areas Affected

Please check all that apply:

• Email Integration (Gmail, IMAP, etc.)
• User Interface/Experience
• Authentication/Authorization
• Data Storage/Management
• API Endpoints
• Documentation
• Testing Infrastructure
• Development Workflow
• Deployment/Infrastructure

Testing Done

Describe the tests you've done:

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed
• Cross-browser testing (if UI changes)
• Mobile responsiveness verified (if UI changes)

Security Considerations

For changes involving data or authentication:

• No sensitive data is exposed
• Authentication checks are in place
• Input validation is implemented
• Rate limiting is considered (if applicable)

Checklist

• I have read the CONTRIBUTING document
• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have commented my code, particularly in complex areas
• I have updated the documentation
• My changes generate no new warnings
• I have added tests that prove my fix/feature works
• All tests pass locally
• Any dependent changes are merged and published

Additional Notes

Add any other context about the pull request here.

Screenshots/Recordings

---

By submitting this pull request, I confirm that my contribution is made under the terms of the project's license.

[Copilot]

Pull request overview

Updates local database docker-compose configuration to use the official Valkey image instead of the Bitnami image (which is no longer available at the referenced tag/registry path).

Changes:

• Switch valkey service image from docker.io/bitnami/valkey:8.0 to valkey/valkey:8.0.

Comments suppressed due to low confidence (1)

docker-compose.db.yaml:22

• Switching from Bitnami to the official valkey/valkey image likely makes ALLOW_EMPTY_PASSWORD and VALKEY_DISABLE_COMMANDS ineffective (those env vars are Bitnami-specific). If you still need these behaviors, configure them via Valkey/Redis config (e.g., requirepass / ACLs and rename-command/disabled commands) or adjust the container command to pass the appropriate flags.

    image: valkey/valkey:8.0
    environment:
      - ALLOW_EMPTY_PASSWORD=yes
      - VALKEY_DISABLE_COMMANDS=FLUSHDB,FLUSHALL
    ports:

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

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.