teyfix/redis repository overview

⁠Redis bundle

teyfix/redis runs Redis and an optional redis-exporter through the shared bootstrap and Process Compose. Mount YAML at /config/redis.yaml (override REDIS_CONFIG). Native data stays at /data; native text logs go to /var/log/redis, overridable through paths.log and readable by an external Vector collector.

See configuration⁠ and Compose⁠. Passwords use {from_env: REDIS_PASSWORD} by default, or {from_file: /run/secrets/password}. The default Redis user requires that password. The exporter has its own generated password and restricted ACL: standard health/statistics commands, no application-key reads/writes or configuration mutations. It exposes port 9121 when metrics.enabled: true (default false); readiness requires a successful redis_up 1 scrape. Redis listens on port 6379.

memory.max defaults to 256mb; memory.policy defaults to noeviction and accepts Redis's standard LRU/LFU/random/TTL policies. persistence.appendonly defaults to false, appendfsync to everysec (always/no also supported), and snapshots to [{seconds: 60, changes: 1}]. Use snapshots: [] to disable RDB snapshots. log_level defaults to notice, with debug, verbose and warning available. Keep the container RAM limit above maxmemory to accommodate Redis and persistence overhead.

Configuration and passwords reconcile at restart; existing native persistence is retained. The image does not delete application keys. Both exporter states, authentication, password rotation, persistence, memory options and shutdown are exercised by docker buildx bake redis-smoke on each published architecture. Run Compose from the project root; bind-mounted .state survives docker compose down -v and requires scoped cleanup for a reset.

Under BuildKit's QEMU emulator, the smoke fixture suppresses Redis's ARM64-COW-BUG warning through a fixture-only wrapper: the kernel probe inspects host /proc mappings while running with guest addresses. Native smoke checks and the published runtime retain the normal kernel check. Authentication, exporter permissions and persistence checks still run under emulation.

Maintained from the source documentation⁠. See published tags⁠ and the service integration guide⁠.