armhf/memcached repository overview

⁠DEPRECATED

The armhf⁠ organization is deprecated in favor of the more-specific arm32v7⁠ and arm32v6⁠ organizations, as per https://github.com/docker-library/official-images#architectures-other-than-amd64⁠. Please adjust your usages accordingly.

⁠Supported tags and respective Dockerfile links

** THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289⁠ IS STILL IN-PROGRESS (which is the first step towards proper multiarch images) **

** PLEASE DO NOT USE THEM FOR IMPORTANT THINGS **

This image is built from the source of the official image of the same name (memcached)⁠. Please see that image's description for links to the relevant Dockerfiles.

If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the tianon/jenkins-groovy GitHub repository⁠, which are responsible for creating the Jenkins jobs which build them.

⁠Quick reference

• Where to get help:
  the Docker Community Forums⁠, the Docker Community Slack⁠, or Stack Overflow⁠

• Where to file issues:
  https://github.com/docker-library/memcached/issues⁠

• Maintained by:
  the Docker Community⁠

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

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

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

• Supported Docker versions:
  the latest release⁠ (down to 1.6 on a best-effort basis)

⁠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.

⁠How to use this image

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

Start your memcached container with the above command and then you can connect you app to it with standard linking:

$ docker run --link my-memcache:memcache -d my-app-image

The memcached server information would then be available through the ENV variables generated by the link as well as through DNS as memcache from /etc/hosts.

How to set the memory usage for memcached

$ docker run --name my-memcache -d memcached memcached -m 64

This would set the memcache server to use 64 megabytes for storage.

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

⁠License

View license information⁠ for the software contained in this image.