Redis Alpine VS Redis Bullseye for using an image without further modifications as a service in Docker Compose

[simon-liebehenschel]

You have no "Discussions" functiobality enabled in this repository, so sorry for a question.

I install nothing into a Redis Docker image and I use it only in docker-compose.yaml as a service. Are there any disadvantages of Alpine image?

Does redis:alpine and redis:bullseye give the same functionality and performance when used as a service? Or there are some pitfalls that are not mentioned on a Redis Docker Image page?

Thank you in advance.

[Jintao Zhang]

bullseye means it base on Debian os.

So your question is similar to Debian vs Alpine.

FYI

• https://stackshare.io/stackups/alpine-linux-vs-debian

• https://www.reddit.com/r/docker/comments/77zork/alpine_vs_debianubuntu_securitywise/

[Tianon Gravi]

Also, from https://hub.docker.com/_/redis:

redis:<version>-alpine

This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.

This variant is useful when final image size being as small as possible is your primary concern. The main caveat to note is that it does use musl libc instead of glibc and friends, so software will often run into issues depending on the depth of their libc requirements/assumptions. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.

To minimize image size, it's uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).

and:

• Where to get help:
  the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow