Migrating to Redict containers #

For complete details on installing and using Redict containers, see Usage with containers.

Redict differs from Redis® container in that the “latest” image and images based on it (e.g. “7.3.0”) refer to images based on “scratch” rather than Debian. Debian- and Alpine-based containers are available and broadly compatible with Redis® containers, but you may wish to consider the opportunity to migrate to a scratch container if you do not depend on any Debian- or Alpine-specific features being available.

We also offer a compatibility image that is based on Debian Bookworm. The difference between the two is that the compatibility image includes symlinks to the Redis® binary names. That is, you can run Redis® commands such as redis-server and redis-cli in a Redict container. This is a stop-gap measure offered as a convenience for those who wish to use the image, for example, in a Helm chart that presupposes that the binaries are named in a certain way. We do recommend that you use the Redict containers if possible and take the opportunity to migrate any Helm charts or other infrastructure to the appropriate Redict containers.

Compatibility notes #

The following notable differences exist between Redis® and Redict containers:

• Redict containers never run as root. We use USER directives rather than gosu.
• Redict containers include software bill of materials (SBOM) in the SPDX text format at
  /usr/local/redict.spdx.txt. It is generated from the Redict source code using REUSE. It is more comprehensive than the JSON SBOM included in the Redis® images.

Compatibility table #

The following table lists the Redict containers most closely compatible with the indicated Redis® container image.