memcached Docker 镜像 - 轩辕镜像

Quick reference

• Maintained by:
  the Docker Community

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

Supported tags and respective Dockerfile links

• 1.6.40, 1.6, 1, latest, 1.6.40-trixie, 1.6-trixie, 1-trixie, trixie

• 1.6.40-alpine, 1.6-alpine, 1-alpine, alpine, 1.6.40-alpine3.23, 1.6-alpine3.23, 1-alpine3.23, alpine3.23

Quick reference (cont.)

• Where to file issues:
  [***]

• Supported architectures: (more info)
  amd64, arm32v5, arm32v6, arm32v7, arm64v8, i386, ppc64le, riscv64, s390x

• Published image artifact details:
  repo-info repo's repos/memcached/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images repo's library/memcached label
  official-images repo's library/memcached file (history)

• Source of this description:
  docs repo's memcached/ directory (history)

What is Memcached?

Memcached is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.

Memcached's APIs provide a very large hash table distributed across multiple machines. When the table is full, subsequent inserts cause older data to be purged in least recently used order. Applications using Memcached typically layer requests and additions into RAM before falling back on a slower backing store, such as a database.

***.org/wiki/Memcached

How to use this image

console
$ docker run --name my-memcache -d memcached

Configuration

To customize the configuration of the memcached server, first obtain the upstream configuration options from the container:

console
$ docker run --rm memcached -h

Using docker run:

console
$ docker run --name my-memcache -d memcached memcached --memory-limit=64

or using Docker Compose:

yaml
services:
  memcached:
    image: memcached
    command:
      - --conn-limit=1024
      - --memory-limit=64
      - --threads=4

For infomation on configuring your memcached server, see the extensive wiki.

Image Variants

The memcached images come in many flavors, each designed for a specific use case.

memcached:<version>

This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.

Some of these tags may have names like trixie in them. These are the suite code names for releases of Debian and indicate which release the image is based on. If your image needs to install any additional packages beyond what comes with the image, you'll likely want to specify one of these explicitly to minimize breakage when there are new releases of Debian.

memcached:<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).

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's memcached/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.