HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
redis
docker-library-redis
Shell2016–2021
redis / docker-library-redis

docker-library-redis

Docker Official Image packaging for Redis

4Distinct people
5Mentions
0Explicit recommenders
1.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Docker Official Image packaging for Redis

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year5 dated mentions

Observed mentions: 2016-05-06 12:52:12 UTC to 2021-06-24 08:16:56 UTC.

0122016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

5 sources
A Dockerfile is not a reproducible set of build instructions in most cases. I'd guess that the vast majority of Dockerfiles are not reproducible. Let's look at an example dockerfile for redis (based on [0]) FROM debian:buster-slim RUN apt-get update; apt-get install -y --no-install-recommends gcc RUN wget http://download.redis.io/releases/redis-6.0.6.tar.gz && tar xvf redis* && cd redis-6.0.6 && make install (Note, modified from upstream for this example; won't actually build) The unreproducible bits are the following: 1. FROM debian:buster-slim -- unreproducible, the base image may change 2. apt-get update && apt-get install -- unreproducible, will give a different version of gcc and other apt packages at different times Those two bits of unreprodicble-ness are so core to the image, that they result in every other step not b
Read the rest
eing reproducible either. As a result, when you 'docker build' that over time, it's very unlikely you'll get a bit-for-bit identical redis binary at the other end. Even a minor gcc version change will likely result in a different binary. As a contrast to this, let's look at a reproducible build of redis using nix. In nixpkgs, it looks like so [1]. If I want a reproducible shell environment, I simply have to pin down its dependencies, which can be done by the following: let pkgs = import (builtins.fetchTarball { url = "https://github.com/NixOS/nixpkgs/archive/48dfc9fa97d762bce28cc8372a2dd3805d14c633.…"; sha256 = "0mqq9hchd8mi1qpd23lwnwa88s67ac257k60hsv795446y7dlld2"; }) {}; in pkgs.mkShell { buildInputs = [ pkgs.redis]; } If I distribute that nix expression, and say "I ran it with nix version 2.3", that is sufficient for anyone to get a bit-for-bit identical redis binary. Even if the binary cache (which lets me not compile it) were to go away, that nixpkgs revision expresses the build instructions, including the exact version of gcc. Sure, if the binary cache were deleted, it would take multiple hours for everything to compile, but I'd still end up with a bit-for-bit identical copy of redis. This is true of the majority of nix packages. All commands are run in a sandbox with no access to most of the filesystem or network, encouraging reproducibility. Network access is mediated by special functions (like fetchTarball and fetchGit) which require including a sha256. All network access going through those specially denoted means of network IO means it's very easy to back up all dependencies (i.e. the redis source code referenced in [1]), and the sha256 means it's easy to use mirrors without having to trust them to be unmodified. It's possible to make an unreproducible nix package, but it requires going out of your way to do so, and rarely happens in practice. Conversely, it's possible to make a reproducible dockerfile, but it requires going out of your way to do so, and rarely happens in practice. Oh, and for bonus points, you can build reproduible docker images using nix. This post has a good intro to how to play with that [2]. [0]: https://github.com/docker-library/redis/blob/bfd904a808cf68d... [1]: https://github.com/NixOS/nixpkgs/blob/a7832c42da266857e98516... [2]: https://christine.website/blog/i-was-wrong-about-nix-2020-02...
In Docker update ToS: Image retention limits imposed on free accounts
To expand on that topic: You can find all the Dockerfiles of the official images linked at the very top on Docker Hub [1]. Once my pull request is merged a Docker-Redis maintainer will have to open another pull request to update the references of the official image on Docker hub [2]. In fact I already updated the Redis Docker image once. You can see the full process there [3]. [1] https://hub.docker.com/_/redis/ [2] https://github.com/docker-library/official-images/pulls [3] https://github.com/docker-library/redis/pull/25
In Redis 3.2.0 is out

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.