Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

memcached.org

docker run --name memcached bitnami/memcached:latest

$ curl -sSL https://raw.githubusercontent.com/bitnami/bitnami-docker-memcached/master/docker-compose.yml > docker-compose.yml
$ docker-compose up -d

• Bitnami closely tracks upstream source changes and promptly publishes new versions of this image using our automated systems.
• With Bitnami images the latest bug fixes and features are available as soon as possible.
• Bitnami containers, virtual machines and cloud images use the same components and configuration approach - making it easy to switch between formats based on your project needs.
• All our images are based on minideb a minimalist Debian based container image which gives you a small base container image and the familiarity of a leading linux distribution.
• All Bitnami images available in Docker Hub are signed with Docker Content Trust (DTC). You can use DOCKER_CONTENT_TRUST=1 to verify the integrity of the images.
• Bitnami container images are released daily with the latest distribution packages available.

This CVE scan report contains a security report with all open CVEs. To get the list of actionable security issues, find the "latest" tag, click the vulnerability report link under the corresponding "Security scan" field and then select the "Only show fixable" filter on the next page.

Deploying Bitnami applications as Helm Charts is the easiest way to get started with our applications on Kubernetes. Read more about the installation in the Bitnami Memcached Chart GitHub repository.

Bitnami containers can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Non-root container images add an extra layer of security and are generally recommended for production environments. However, because they run as a non-root user, privileged tasks are typically off-limits. Learn more about non-root containers in our docs.

NOTE: Debian 8 images have been deprecated in favor of Debian 9 images. Bitnami will not longer publish new Docker images based on Debian 8.

Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags in our documentation page.

• 1-ol-7, 1.5.16-ol-7-r34 (1/ol-7/Dockerfile)
• 1-debian-9, 1.5.16-debian-9-r34, 1, 1.5.16, 1.5.16-r34, latest (1/debian-9/Dockerfile)
• 1-rhel-7, 1.5.13-rhel-7-r0 (1/rhel-7/Dockerfile)

Subscribe to project updates by watching the bitnami/memcached GitHub repo.

The recommended way to get the Bitnami Memcached Docker Image is to pull the prebuilt image from the Docker Hub Registry.

docker pull bitnami/memcached:latest

To use a specific version, you can pull a versioned tag. You can view the list of available versions in the Docker Hub Registry.

docker pull bitnami/memcached:[TAG]

If you wish, you can also build the image yourself.

docker build -t bitnami/memcached:latest https://github.com/bitnami/bitnami-docker-memcached.git

Using Docker container networking, a Memcached server running inside a container can easily be accessed by your application containers.

Containers attached to the same network can communicate with each other using the container name as the hostname.

$ docker network create app-tier --driver bridge

Use the --network app-tier argument to the docker run command to attach the Memcached container to the app-tier network.

$ docker run -d --name memcached-server \
    --network app-tier \
    bitnami/memcached:latest

$ docker run -d --name myapp \
    --network app-tier \
    YOUR_APPLICATION_IMAGE

IMPORTANT:

1. Please update the YOUR_APPLICATION_IMAGE_ placeholder in the above snippet with your application image
2. In your application container, use the hostname memcached-server to connect to the Memcached server

When not specified, Docker Compose automatically sets up a new network and attaches all deployed services to that network. However, we will explicitly define a new bridge network named app-tier. In this example we assume that you want to connect to the Memcached server from your own custom application image which is identified in the following snippet by the service name myapp.

version: '2'

networks:
  app-tier:
    driver: bridge

services:
  memcached:
    image: 'bitnami/memcached:latest'
    networks:
      - app-tier
  myapp:
    image: 'YOUR_APPLICATION_IMAGE'
    networks:
      - app-tier

IMPORTANT:

1. Please update the YOUR_APPLICATION_IMAGE_ placeholder in the above snippet with your application image
2. In your application container, use the hostname memcached to connect to the Memcached server

Launch the containers using:

$ docker-compose up -d

By default, the Bitnami Memcached container starts with a cache size of 64mb. You can specify other value using the MEMCACHED_CACHE_SIZE environment variable.

docker run --name memcached -e MEMCACHED_CACHE_SIZE=128 bitnami/memcached:latest

or using Docker Compose:

version: '2'

services:
  memcached:
    image: 'bitnami/memcached:latest'
    ports:
      - '11211:11211'
    environment:
      - MEMCACHED_CACHE_SIZE=128

The default value of the MEMCACHED_CACHE_SIZE is 64.

Authentication on the Memcached server is disabled by default. To enable authentication, specify a username and password for the Memcached admin user using the MEMCACHED_USERNAME and MEMCACHED_PASSWORD environment variables.

docker run --name memcached \
  -e MEMCACHED_USERNAME=my_user \
  -e MEMCACHED_PASSWORD=my_password \
  bitnami/memcached:latest

or using Docker Compose:

version: '2'

services:
  memcached:
    image: 'bitnami/memcached:latest'
    ports:
      - '11211:11211'
    environment:
      - MEMCACHED_USERNAME=my_user
      - MEMCACHED_PASSWORD=my_password

The default value of the MEMCACHED_USERNAME is root.

The Bitnami Memcached Docker image sends the container logs to the stdout. To view the logs:

docker logs memcached

or using Docker Compose:

docker-compose logs memcached

You can configure the containers logging driver using the --log-driver option if you wish to consume the container logs differently. In the default configuration docker uses the json-file driver.

Bitnami provides up-to-date versions of Memcached, including security patches, soon after they are made upstream. We recommend that you follow these steps to upgrade your container.

docker pull bitnami/memcached:latest

or if you're using Docker Compose, update the value of the image property to bitnami/memcached:latest.

docker rm -v memcached

or using Docker Compose:

docker-compose rm -v memcached

Re-create your container from the new image.

docker run --name memcached bitnami/memcached:latest

or using Docker Compose:

docker-compose up memcached

• The memcached container has been migrated to a non-root container approach. Previously the container run as root user and the memcached daemon was started as memcached user. From now own, both the container and the memcached daemon run as user 1001. As a consequence, the configuration files are writable by the user running the memcached process.

• MEMCACHED_USER parameter has been renamed to MEMCACHED_USERNAME.

• The logs are always sent to the stdout and are no longer collected in the volume.

We'd love for you to contribute to this container. You can request new features by creating an issue, or submit a pull request with your contribution.

If you encountered a problem running this container, you can file an issue. For us to provide better support, be sure to include the following information in your issue:

• Host OS and version
• Docker version (docker version)
• Output of docker info
• Version of this container (echo $BITNAMI_IMAGE_VERSION inside the container)
• The command you used to run the container, and any relevant output you saw (masking any sensitive information)

Copyright (c) 2015-2019 Bitnami

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.