memcached 1.5
Features
Download this image
Description
memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load.
Usage
$ docker run -d --name memcached -p 11211:11211 rhel8/memcached
Command-line options supported by memcached may be specified as arguments of
the run command. For example, the following command increases the maximum
amount of memory to 128 megabytes and enables debug messages:
$ docker run -d --name memcached -p 11211:11211 rhel8/memcached -m 128 -vv
Environment variables
memcached started in the container can be also configured with the
following environment variables:
MEMCACHED_MAX_MEMORY
Specify the maximum amount of memory used for object storage in
megabytes. The default value is 64 megabytes.
MEMCACHED_MAX_CONNECTIONS
Specify the maximum number of client connections. The default value is
1024.
MEMCACHED_SLAB_PAGE_SIZE
Specify the default size of the slab page. The default value is 1m.
MEMCACHED_EXTRA_PARAMETERS
Specify any command-line options supported by memcached.
Documentation
Products using this container
Image specifications
The following information was extracted from the dockerfile and other sources.
| Canonical image ID | memcached 1.5 |
| Summary | High-performance memory object caching system |
| Description | memcached is a high-performance, distributed memory object caching system, generic in nature, but intended for use in speeding up dynamic web applications by alleviating database load. |
| Provider | Red Hat |
| Maintainer | tkorbar@redhat.com |
| Repository name | rhel10/memcached |
| Image version | 10.1 |
| Architecture | amd64 |
| Usage | podman run -d --name memcached -p 11211:11211 rhel10/memcached |
| Exposed ports | 11211:memcached |
Registry tokens
Use a registry service account token to authenticate your container client. This allows you to pull images without using your personal Red Hat credentials, which is recommended for CI/CD pipelines and automated deployments.
Using Podman login
Run the following command, then enter your registry token credentials when prompted by the terminal.
Pull the image
Image identifiers
Red Hat login
Use the following instructions to get images from a Red Hat container registry using your Red Hat login.
Using Podman login
Run the following command, then enter your login credentials when prompted by the terminal.
Pull the image
Image identifiers
Unauthenticated
Use the following instructions to get images from a Red Hat container registry without providing authentication.
Using podman
Use the following command(s) from a system with podman installed.
Image identifiers
Getting source containers
Source code is available for all Red Hat UBI-based images in the form of downloadable containers. Here are a few things you should know about Red Hat source containers.
- Although they are packaged as containers, source containers cannot be run. So instead of using podman pull to get them to your system, use the skopeo command.
- Source containers are named based on the binary containers they represent. So, for example, to get the source container for a particular standard RHEL UBI 8 container (registry.access.redhat.com/ubi8/ubi8.1-397) you simply append -source to get the source code container for that image (registry.access.redhat.com/ubi8/ubi8.1-397-source).
- Once a source container is copied to a local directory, you can use a combination of tar,gzip, and rpm commands to work with that content.
Step one
Use skopeo to copy the source image to a local directory
Step two
Inspect the image
Step three
Untar the contents
Step four
Begin examining and using the content.
